[Buildroot] Compiling buildroot for Arm "Armada 166E" Target

[Buildroot] Compiling buildroot for Arm "Armada 166E" Target

[Aseem Sharma]

Hi,

I am naive to buildroot & processor world trying to compile
"buildroot-2017.02.5" for "Marvell ARM Armada 166E processor (compatible to
ARMv5TE instruction-set)" based old system. However, I do not understand
the options to be selected in "make menuconfig" for
1. Target options->Target Architecture {think should be ARM - little endian}
2. Target options->Target Architecture variant

Thanks in advance for your help.

Best Regards,
Aseem
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20170809/a5d1dee9/attachment.html>

[Buildroot] Compiling buildroot for Arm "Armada 166E" Target

[Arnout Vandecappelle]

On 09-08-17 14:30, Aseem Sharma wrote:
> Hi,
> 
> I am naive to buildroot & processor world trying to compile
> "buildroot-2017.02.5" for "Marvell ARM Armada 166E processor (compatible to
> ARMv5TE instruction-set)" based old system. However, I do not understand the
> options to be selected in "make menuconfig" for 
> 1. Target options->Target Architecture {think should be ARM - little endian}
> 2. Target options->Target Architecture variant

 It is indeed sometimes difficult to find out what the underlying CPU
architecture is for a given SoC. Also, we only have 40-ish variants while gcc
supports something like 100 variants. Anyway, for your CPU, it is certainly ARM
little endian, and most likely xscale variant, though arm926t should work as well.

 You probably need to keep VFP support turned off, but I can't find a reference
that confirms that this CPU is lacking a floating point unit.

 You'll also need some figuring out to find a kernel configuration that works...
Can't help you there, I'm afraid.

 Regards,
 Arnout

-- 
Arnout Vandecappelle                          arnout at mind be
Senior Embedded Software Architect            +32-16-286500
Essensium/Mind                                http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium           BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint:  7493 020B C7E3 8618 8DEC 222C 82EB F404 F9AC 0DDF

[Buildroot] Compiling buildroot for Arm "Armada 166E" Target

[Baruch Siach]

Hi Aweem,

On Wed, Aug 09, 2017 at 06:00:55PM +0530, Aseem Sharma wrote:
> I am naive to buildroot & processor world trying to compile
> "buildroot-2017.02.5" for "Marvell ARM Armada 166E processor (compatible to
> ARMv5TE instruction-set)" based old system. However, I do not understand
> the options to be selected in "make menuconfig" for
> 1. Target options->Target Architecture {think should be ARM - little endian}
> 2. Target options->Target Architecture variant
> 
> Thanks in advance for your help.

Based on the Armada 16x Datasheet[1], the mainline kernel 
arch/arm/mach-mmp/Kconfig (CONFIG_CPU_PXA168) and arch/arm/Kconfig 
(CONFIG_IWMMXT), it seems like you need the iwmmxt ARM variant for your Armada 
166E processor.

[1] http://www.marvell.com.cn/application-processors/armada-100/assets/armada_16x_datasheet.pdf

baruch

-- 
     http://baruch.siach.name/blog/                  ~. .~   Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
   - baruch at tkos.co.il - tel: +972.52.368.4656, http://www.tkos.co.il -

[Buildroot] Compiling buildroot for Arm "Armada 166E" Target

[Aseem Sharma]

Hello Baruch & Arnout,

Thanks for your responses.
The board that I have is quite old with limited RAM and Flash.

Baruch,
Could you please provide more details as to how do I select "iwmmxt" using
menuconfig. As far as I remember, I do not seem to have that option in my
current buildroot release.

Also, as per Arnout's response to my query, I should be using ARM little
endian with arm926tARM.

Are these two options one and the same?
Thanks in advance.

Best Regards,
Aseem

Sent via really tiny keyboard. Expect random auto corrects, fat finger
typos and weirdness!!


On 09-Aug-2017 21:19, "Baruch Siach" <baruch@tkos.co.il> wrote:

Hi Aweem,

On Wed, Aug 09, 2017 at 06:00:55PM +0530, Aseem Sharma wrote:
> I am naive to buildroot & processor world trying to compile
> "buildroot-2017.02.5" for "Marvell ARM Armada 166E processor (compatible
to
> ARMv5TE instruction-set)" based old system. However, I do not understand
> the options to be selected in "make menuconfig" for
> 1. Target options->Target Architecture {think should be ARM - little
endian}
> 2. Target options->Target Architecture variant
>
> Thanks in advance for your help.

Based on the Armada 16x Datasheet[1], the mainline kernel
arch/arm/mach-mmp/Kconfig (CONFIG_CPU_PXA168) and arch/arm/Kconfig
(CONFIG_IWMMXT), it seems like you need the iwmmxt ARM variant for your
Armada
166E processor.

[1] http://www.marvell.com.cn/application-processors/armada-100/
assets/armada_16x_datasheet.pdf

baruch

--
     http://baruch.siach.name/blog/                  ~. .~   Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
   - baruch at tkos.co.il - tel: +972.52.368.4656, http://www.tkos.co.il -
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20170809/a9d218b6/attachment.html>

[Buildroot] Compiling buildroot for Arm "Armada 166E" Target

[Baruch Siach]

Hi Aseem,

On Wed, Aug 09, 2017 at 10:03:24PM +0530, Aseem Sharma wrote:
> Hello Baruch & Arnout,
> 
> Thanks for your responses.
> The board that I have is quite old with limited RAM and Flash.
> 
> Baruch,
> Could you please provide more details as to how do I select "iwmmxt" using
> menuconfig. As far as I remember, I do not seem to have that option in my
> current buildroot release.

Go to 'Target options' -> 'Target Architecture Variant', and select 'iwmmxt' 
(last option).

> Also, as per Arnout's response to my query, I should be using ARM little
> endian with arm926tARM.

As far as I know arm926t code is compatible with iwmmxt, but not the other way 
around. Look for Sheeva PJ1 at [1]. See also [2].

[1] https://en.wikipedia.org/wiki/List_of_ARM_microarchitectures

[2] https://en.wikipedia.org/wiki/MMX_(instruction_set)#MMX_in_embedded_applications

> Are these two options one and the same?

I don't think so.

baruch

> Thanks in advance.
> 
> Best Regards,
> Aseem
> 
> Sent via really tiny keyboard. Expect random auto corrects, fat finger
> typos and weirdness!!
> 
> 
> On 09-Aug-2017 21:19, "Baruch Siach" <baruch@tkos.co.il> wrote:
> 
> Hi Aweem,
> 
> On Wed, Aug 09, 2017 at 06:00:55PM +0530, Aseem Sharma wrote:
> > I am naive to buildroot & processor world trying to compile
> > "buildroot-2017.02.5" for "Marvell ARM Armada 166E processor (compatible
> to
> > ARMv5TE instruction-set)" based old system. However, I do not understand
> > the options to be selected in "make menuconfig" for
> > 1. Target options->Target Architecture {think should be ARM - little
> endian}
> > 2. Target options->Target Architecture variant
> >
> > Thanks in advance for your help.
> 
> Based on the Armada 16x Datasheet[1], the mainline kernel
> arch/arm/mach-mmp/Kconfig (CONFIG_CPU_PXA168) and arch/arm/Kconfig
> (CONFIG_IWMMXT), it seems like you need the iwmmxt ARM variant for your
> Armada
> 166E processor.
> 
> [1] http://www.marvell.com.cn/application-processors/armada-100/
> assets/armada_16x_datasheet.pdf

-- 
     http://baruch.siach.name/blog/                  ~. .~   Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
   - baruch at tkos.co.il - tel: +972.52.368.4656, http://www.tkos.co.il -

[Buildroot] Compiling buildroot for Arm "Armada 166E" Target

[Aseem Sharma]

Thanks Baruch & Arnout. Will give a try.

Best Regards,
Aseem

On Wed, Aug 9, 2017 at 10:47 PM, Baruch Siach <baruch@tkos.co.il> wrote:

> Hi Aseem,
>
> On Wed, Aug 09, 2017 at 10:03:24PM +0530, Aseem Sharma wrote:
> > Hello Baruch & Arnout,
> >
> > Thanks for your responses.
> > The board that I have is quite old with limited RAM and Flash.
> >
> > Baruch,
> > Could you please provide more details as to how do I select "iwmmxt"
> using
> > menuconfig. As far as I remember, I do not seem to have that option in my
> > current buildroot release.
>
> Go to 'Target options' -> 'Target Architecture Variant', and select
> 'iwmmxt'
> (last option).
>
> > Also, as per Arnout's response to my query, I should be using ARM little
> > endian with arm926tARM.
>
> As far as I know arm926t code is compatible with iwmmxt, but not the other
> way
> around. Look for Sheeva PJ1 at [1]. See also [2].
>
> [1] https://en.wikipedia.org/wiki/List_of_ARM_microarchitectures
>
> [2] https://en.wikipedia.org/wiki/MMX_(instruction_set)#MMX_in_
> embedded_applications
>
> > Are these two options one and the same?
>
> I don't think so.
>
> baruch
>
> > Thanks in advance.
> >
> > Best Regards,
> > Aseem
> >
> > Sent via really tiny keyboard. Expect random auto corrects, fat finger
> > typos and weirdness!!
> >
> >
> > On 09-Aug-2017 21:19, "Baruch Siach" <baruch@tkos.co.il> wrote:
> >
> > Hi Aweem,
> >
> > On Wed, Aug 09, 2017 at 06:00:55PM +0530, Aseem Sharma wrote:
> > > I am naive to buildroot & processor world trying to compile
> > > "buildroot-2017.02.5" for "Marvell ARM Armada 166E processor
> (compatible
> > to
> > > ARMv5TE instruction-set)" based old system. However, I do not
> understand
> > > the options to be selected in "make menuconfig" for
> > > 1. Target options->Target Architecture {think should be ARM - little
> > endian}
> > > 2. Target options->Target Architecture variant
> > >
> > > Thanks in advance for your help.
> >
> > Based on the Armada 16x Datasheet[1], the mainline kernel
> > arch/arm/mach-mmp/Kconfig (CONFIG_CPU_PXA168) and arch/arm/Kconfig
> > (CONFIG_IWMMXT), it seems like you need the iwmmxt ARM variant for your
> > Armada
> > 166E processor.
> >
> > [1] http://www.marvell.com.cn/application-processors/armada-100/
> > assets/armada_16x_datasheet.pdf
>
> --
>      http://baruch.siach.name/blog/                  ~. .~   Tk Open
> Systems
> =}------------------------------------------------ooO--U--
> Ooo------------{=
>    - baruch at tkos.co.il - tel: +972.52.368.4656, http://www.tkos.co.il -
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20170810/f041f582/attachment.html>

[Buildroot] Compiling buildroot for Arm "Armada 166E" Target

[Aseem Sharma]

Hello Baruch/Arnout,

*A follow-up question:*
I selected 'iwmmxt' as per Baruch's suggestion and tried to run "make".
The build seems to be failing with following error message in
"busybox-1.26.2" compilation:

util-linux/mkfs_ext2.c: In function ?mkfs_ext2_main?:
util-linux/mkfs_ext2.c:715:1: error: insn does not satisfy its constraints:
 }
 ^
(insn 1169 286 287 31 (set (reg:SI 0 r0)
        (reg:SI 80 wr0)) util-linux/mkfs_ext2.c:344 426 {*iwmmxt_movsi_insn}
     (nil))
util-linux/mkfs_ext2.c:715:1: internal compiler error: in
reload_cse_simplify_operands, at postreload.c:411
Please submit a full bug report,
with preprocessed source if appropriate.
See <http://bugs.buildroot.net/> for instructions.
scripts/Makefile.build:197: recipe for target 'util-linux/mkfs_ext2.o'
failed
make[2]: *** [util-linux/mkfs_ext2.o] Error 1
Makefile:742: recipe for target 'util-linux' failed
make[1]: *** [util-linux] Error 2
make[1]: Leaving directory '/home/administrator/Downloads/buildroot_2017/
buildroot-2017.02.5/output/build/busybox-1.26.2'
package/pkg-generic.mk:216: recipe for target '/home/administrator/
Downloads/buildroot_2017/buildroot-2017.02.5/output/
build/busybox-1.26.2/.stamp_built' failed
make: *** [/home/administrator/Downloads/buildroot_2017/
buildroot-2017.02.5/output/build/busybox-1.26.2/.stamp_built] Error 2

It would be really helpful is you can provide some insight and possibly a
fix/workaround.

Thanks & Regards,
Aseem

On Thu, Aug 10, 2017 at 8:55 AM, Aseem Sharma <aseem.sharma19@gmail.com>
wrote:

> Thanks Baruch & Arnout. Will give a try.
>
> Best Regards,
> Aseem
>
> On Wed, Aug 9, 2017 at 10:47 PM, Baruch Siach <baruch@tkos.co.il> wrote:
>
>> Hi Aseem,
>>
>> On Wed, Aug 09, 2017 at 10:03:24PM +0530, Aseem Sharma wrote:
>> > Hello Baruch & Arnout,
>> >
>> > Thanks for your responses.
>> > The board that I have is quite old with limited RAM and Flash.
>> >
>> > Baruch,
>> > Could you please provide more details as to how do I select "iwmmxt"
>> using
>> > menuconfig. As far as I remember, I do not seem to have that option in
>> my
>> > current buildroot release.
>>
>> Go to 'Target options' -> 'Target Architecture Variant', and select
>> 'iwmmxt'
>> (last option).
>>
>> > Also, as per Arnout's response to my query, I should be using ARM little
>> > endian with arm926tARM.
>>
>> As far as I know arm926t code is compatible with iwmmxt, but not the
>> other way
>> around. Look for Sheeva PJ1 at [1]. See also [2].
>>
>> [1] https://en.wikipedia.org/wiki/List_of_ARM_microarchitectures
>>
>> [2] https://en.wikipedia.org/wiki/MMX_(instruction_set)#MMX_in_e
>> mbedded_applications
>>
>> > Are these two options one and the same?
>>
>> I don't think so.
>>
>> baruch
>>
>> > Thanks in advance.
>> >
>> > Best Regards,
>> > Aseem
>> >
>> > Sent via really tiny keyboard. Expect random auto corrects, fat finger
>> > typos and weirdness!!
>> >
>> >
>> > On 09-Aug-2017 21:19, "Baruch Siach" <baruch@tkos.co.il> wrote:
>> >
>> > Hi Aweem,
>> >
>> > On Wed, Aug 09, 2017 at 06:00:55PM +0530, Aseem Sharma wrote:
>> > > I am naive to buildroot & processor world trying to compile
>> > > "buildroot-2017.02.5" for "Marvell ARM Armada 166E processor
>> (compatible
>> > to
>> > > ARMv5TE instruction-set)" based old system. However, I do not
>> understand
>> > > the options to be selected in "make menuconfig" for
>> > > 1. Target options->Target Architecture {think should be ARM - little
>> > endian}
>> > > 2. Target options->Target Architecture variant
>> > >
>> > > Thanks in advance for your help.
>> >
>> > Based on the Armada 16x Datasheet[1], the mainline kernel
>> > arch/arm/mach-mmp/Kconfig (CONFIG_CPU_PXA168) and arch/arm/Kconfig
>> > (CONFIG_IWMMXT), it seems like you need the iwmmxt ARM variant for your
>> > Armada
>> > 166E processor.
>> >
>> > [1] http://www.marvell.com.cn/application-processors/armada-100/
>> > assets/armada_16x_datasheet.pdf
>>
>> --
>>      http://baruch.siach.name/blog/                  ~. .~   Tk Open
>> Systems
>> =}------------------------------------------------ooO--U--Oo
>> o------------{=
>>    - baruch at tkos.co.il - tel: +972.52.368.4656, http://www.tkos.co.il -
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20170810/a68587ad/attachment.html>

[Buildroot] Compiling buildroot for Arm "Armada 166E" Target

[Baruch Siach]

Hi Aseem,

On Thu, Aug 10, 2017 at 11:56:56AM +0530, Aseem Sharma wrote:
> *A follow-up question:*
> I selected 'iwmmxt' as per Baruch's suggestion and tried to run "make".
> The build seems to be failing with following error message in
> "busybox-1.26.2" compilation:
> 
> util-linux/mkfs_ext2.c: In function ?mkfs_ext2_main?:
> util-linux/mkfs_ext2.c:715:1: error: insn does not satisfy its constraints:
>  }
>  ^
> (insn 1169 286 287 31 (set (reg:SI 0 r0)
>         (reg:SI 80 wr0)) util-linux/mkfs_ext2.c:344 426 {*iwmmxt_movsi_insn}
>      (nil))
> util-linux/mkfs_ext2.c:715:1: internal compiler error: in
> reload_cse_simplify_operands, at postreload.c:411
> Please submit a full bug report,
> with preprocessed source if appropriate.
> See <http://bugs.buildroot.net/> for instructions.
> scripts/Makefile.build:197: recipe for target 'util-linux/mkfs_ext2.o'
> failed
> make[2]: *** [util-linux/mkfs_ext2.o] Error 1
> Makefile:742: recipe for target 'util-linux' failed
> make[1]: *** [util-linux] Error 2
> make[1]: Leaving directory '/home/administrator/Downloads/buildroot_2017/
> buildroot-2017.02.5/output/build/busybox-1.26.2'
> package/pkg-generic.mk:216: recipe for target '/home/administrator/
> Downloads/buildroot_2017/buildroot-2017.02.5/output/
> build/busybox-1.26.2/.stamp_built' failed
> make: *** [/home/administrator/Downloads/buildroot_2017/
> buildroot-2017.02.5/output/build/busybox-1.26.2/.stamp_built] Error 2
> 
> It would be really helpful is you can provide some insight and possibly a
> fix/workaround.

Have you done a clean rebuild, i.e., 'make clean; make'? See 
http://nightly.buildroot.org/manual.html#full-rebuild .

baruch

> On Thu, Aug 10, 2017 at 8:55 AM, Aseem Sharma <aseem.sharma19@gmail.com>
> wrote:
> 
> > Thanks Baruch & Arnout. Will give a try.
> >
> > Best Regards,
> > Aseem
> >
> > On Wed, Aug 9, 2017 at 10:47 PM, Baruch Siach <baruch@tkos.co.il> wrote:
> >
> >> Hi Aseem,
> >>
> >> On Wed, Aug 09, 2017 at 10:03:24PM +0530, Aseem Sharma wrote:
> >> > Hello Baruch & Arnout,
> >> >
> >> > Thanks for your responses.
> >> > The board that I have is quite old with limited RAM and Flash.
> >> >
> >> > Baruch,
> >> > Could you please provide more details as to how do I select "iwmmxt"
> >> using
> >> > menuconfig. As far as I remember, I do not seem to have that option in
> >> my
> >> > current buildroot release.
> >>
> >> Go to 'Target options' -> 'Target Architecture Variant', and select
> >> 'iwmmxt'
> >> (last option).
> >>
> >> > Also, as per Arnout's response to my query, I should be using ARM little
> >> > endian with arm926tARM.
> >>
> >> As far as I know arm926t code is compatible with iwmmxt, but not the
> >> other way
> >> around. Look for Sheeva PJ1 at [1]. See also [2].
> >>
> >> [1] https://en.wikipedia.org/wiki/List_of_ARM_microarchitectures
> >>
> >> [2] https://en.wikipedia.org/wiki/MMX_(instruction_set)#MMX_in_e
> >> mbedded_applications
> >>
> >> > Are these two options one and the same?
> >>
> >> I don't think so.
> >>
> >> baruch
> >>
> >> > Thanks in advance.
> >> >
> >> > Best Regards,
> >> > Aseem
> >> >
> >> > Sent via really tiny keyboard. Expect random auto corrects, fat finger
> >> > typos and weirdness!!
> >> >
> >> >
> >> > On 09-Aug-2017 21:19, "Baruch Siach" <baruch@tkos.co.il> wrote:
> >> >
> >> > Hi Aweem,
> >> >
> >> > On Wed, Aug 09, 2017 at 06:00:55PM +0530, Aseem Sharma wrote:
> >> > > I am naive to buildroot & processor world trying to compile
> >> > > "buildroot-2017.02.5" for "Marvell ARM Armada 166E processor
> >> (compatible
> >> > to
> >> > > ARMv5TE instruction-set)" based old system. However, I do not
> >> understand
> >> > > the options to be selected in "make menuconfig" for
> >> > > 1. Target options->Target Architecture {think should be ARM - little
> >> > endian}
> >> > > 2. Target options->Target Architecture variant
> >> > >
> >> > > Thanks in advance for your help.
> >> >
> >> > Based on the Armada 16x Datasheet[1], the mainline kernel
> >> > arch/arm/mach-mmp/Kconfig (CONFIG_CPU_PXA168) and arch/arm/Kconfig
> >> > (CONFIG_IWMMXT), it seems like you need the iwmmxt ARM variant for your
> >> > Armada
> >> > 166E processor.
> >> >
> >> > [1] http://www.marvell.com.cn/application-processors/armada-100/
> >> > assets/armada_16x_datasheet.pdf

-- 
     http://baruch.siach.name/blog/                  ~. .~   Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
   - baruch at tkos.co.il - tel: +972.52.368.4656, http://www.tkos.co.il -

[Buildroot] Compiling buildroot for Arm "Armada 166E" Target

[Aseem Sharma]

Yes Baruch. I tried a couple of times with "make clean" & even "make
distclean". However, the error is consistent.
Found a similar issue here: https://gcc.gnu.org/bugzilla/
show_bug.cgi?id=40836

Best Regards,
Aseem

On Thu, Aug 10, 2017 at 12:06 PM, Baruch Siach <baruch@tkos.co.il> wrote:

> Hi Aseem,
>
> On Thu, Aug 10, 2017 at 11:56:56AM +0530, Aseem Sharma wrote:
> > *A follow-up question:*
> > I selected 'iwmmxt' as per Baruch's suggestion and tried to run "make".
> > The build seems to be failing with following error message in
> > "busybox-1.26.2" compilation:
> >
> > util-linux/mkfs_ext2.c: In function ?mkfs_ext2_main?:
> > util-linux/mkfs_ext2.c:715:1: error: insn does not satisfy its
> constraints:
> >  }
> >  ^
> > (insn 1169 286 287 31 (set (reg:SI 0 r0)
> >         (reg:SI 80 wr0)) util-linux/mkfs_ext2.c:344 426
> {*iwmmxt_movsi_insn}
> >      (nil))
> > util-linux/mkfs_ext2.c:715:1: internal compiler error: in
> > reload_cse_simplify_operands, at postreload.c:411
> > Please submit a full bug report,
> > with preprocessed source if appropriate.
> > See <http://bugs.buildroot.net/> for instructions.
> > scripts/Makefile.build:197: recipe for target 'util-linux/mkfs_ext2.o'
> > failed
> > make[2]: *** [util-linux/mkfs_ext2.o] Error 1
> > Makefile:742: recipe for target 'util-linux' failed
> > make[1]: *** [util-linux] Error 2
> > make[1]: Leaving directory '/home/administrator/
> Downloads/buildroot_2017/
> > buildroot-2017.02.5/output/build/busybox-1.26.2'
> > package/pkg-generic.mk:216: recipe for target '/home/administrator/
> > Downloads/buildroot_2017/buildroot-2017.02.5/output/
> > build/busybox-1.26.2/.stamp_built' failed
> > make: *** [/home/administrator/Downloads/buildroot_2017/
> > buildroot-2017.02.5/output/build/busybox-1.26.2/.stamp_built] Error 2
> >
> > It would be really helpful is you can provide some insight and possibly a
> > fix/workaround.
>
> Have you done a clean rebuild, i.e., 'make clean; make'? See
> http://nightly.buildroot.org/manual.html#full-rebuild .
>
> baruch
>
> > On Thu, Aug 10, 2017 at 8:55 AM, Aseem Sharma <aseem.sharma19@gmail.com>
> > wrote:
> >
> > > Thanks Baruch & Arnout. Will give a try.
> > >
> > > Best Regards,
> > > Aseem
> > >
> > > On Wed, Aug 9, 2017 at 10:47 PM, Baruch Siach <baruch@tkos.co.il>
> wrote:
> > >
> > >> Hi Aseem,
> > >>
> > >> On Wed, Aug 09, 2017 at 10:03:24PM +0530, Aseem Sharma wrote:
> > >> > Hello Baruch & Arnout,
> > >> >
> > >> > Thanks for your responses.
> > >> > The board that I have is quite old with limited RAM and Flash.
> > >> >
> > >> > Baruch,
> > >> > Could you please provide more details as to how do I select "iwmmxt"
> > >> using
> > >> > menuconfig. As far as I remember, I do not seem to have that option
> in
> > >> my
> > >> > current buildroot release.
> > >>
> > >> Go to 'Target options' -> 'Target Architecture Variant', and select
> > >> 'iwmmxt'
> > >> (last option).
> > >>
> > >> > Also, as per Arnout's response to my query, I should be using ARM
> little
> > >> > endian with arm926tARM.
> > >>
> > >> As far as I know arm926t code is compatible with iwmmxt, but not the
> > >> other way
> > >> around. Look for Sheeva PJ1 at [1]. See also [2].
> > >>
> > >> [1] https://en.wikipedia.org/wiki/List_of_ARM_microarchitectures
> > >>
> > >> [2] https://en.wikipedia.org/wiki/MMX_(instruction_set)#MMX_in_e
> > >> mbedded_applications
> > >>
> > >> > Are these two options one and the same?
> > >>
> > >> I don't think so.
> > >>
> > >> baruch
> > >>
> > >> > Thanks in advance.
> > >> >
> > >> > Best Regards,
> > >> > Aseem
> > >> >
> > >> > Sent via really tiny keyboard. Expect random auto corrects, fat
> finger
> > >> > typos and weirdness!!
> > >> >
> > >> >
> > >> > On 09-Aug-2017 21:19, "Baruch Siach" <baruch@tkos.co.il> wrote:
> > >> >
> > >> > Hi Aweem,
> > >> >
> > >> > On Wed, Aug 09, 2017 at 06:00:55PM +0530, Aseem Sharma wrote:
> > >> > > I am naive to buildroot & processor world trying to compile
> > >> > > "buildroot-2017.02.5" for "Marvell ARM Armada 166E processor
> > >> (compatible
> > >> > to
> > >> > > ARMv5TE instruction-set)" based old system. However, I do not
> > >> understand
> > >> > > the options to be selected in "make menuconfig" for
> > >> > > 1. Target options->Target Architecture {think should be ARM -
> little
> > >> > endian}
> > >> > > 2. Target options->Target Architecture variant
> > >> > >
> > >> > > Thanks in advance for your help.
> > >> >
> > >> > Based on the Armada 16x Datasheet[1], the mainline kernel
> > >> > arch/arm/mach-mmp/Kconfig (CONFIG_CPU_PXA168) and arch/arm/Kconfig
> > >> > (CONFIG_IWMMXT), it seems like you need the iwmmxt ARM variant for
> your
> > >> > Armada
> > >> > 166E processor.
> > >> >
> > >> > [1] http://www.marvell.com.cn/application-processors/armada-100/
> > >> > assets/armada_16x_datasheet.pdf
>
> --
>      http://baruch.siach.name/blog/                  ~. .~   Tk Open
> Systems
> =}------------------------------------------------ooO--U--
> Ooo------------{=
>    - baruch at tkos.co.il - tel: +972.52.368.4656, http://www.tkos.co.il -
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20170810/f306cf7c/attachment.html>

[Buildroot] Compiling buildroot for Arm "Armada 166E" Target

[Baruch Siach]

Hi Aseem,

On Thu, Aug 10, 2017 at 12:19:33PM +0530, Aseem Sharma wrote:
> Yes Baruch. I tried a couple of times with "make clean" & even "make
> distclean". However, the error is consistent.
> Found a similar issue here: https://gcc.gnu.org/bugzilla/
> show_bug.cgi?id=40836

This issue seems to be fixed since gcc 4.8.

I could not reproduce this ICE on current master with the following minimal 
defconfig:

BR2_arm=y
BR2_iwmmxt=y

Can you give it a try?

baruch

> On Thu, Aug 10, 2017 at 12:06 PM, Baruch Siach <baruch@tkos.co.il> wrote:
> > On Thu, Aug 10, 2017 at 11:56:56AM +0530, Aseem Sharma wrote:
> > > *A follow-up question:*
> > > I selected 'iwmmxt' as per Baruch's suggestion and tried to run "make".
> > > The build seems to be failing with following error message in
> > > "busybox-1.26.2" compilation:
> > >
> > > util-linux/mkfs_ext2.c: In function ?mkfs_ext2_main?:
> > > util-linux/mkfs_ext2.c:715:1: error: insn does not satisfy its
> > constraints:
> > >  }
> > >  ^
> > > (insn 1169 286 287 31 (set (reg:SI 0 r0)
> > >         (reg:SI 80 wr0)) util-linux/mkfs_ext2.c:344 426
> > {*iwmmxt_movsi_insn}
> > >      (nil))
> > > util-linux/mkfs_ext2.c:715:1: internal compiler error: in
> > > reload_cse_simplify_operands, at postreload.c:411
> > > Please submit a full bug report,
> > > with preprocessed source if appropriate.
> > > See <http://bugs.buildroot.net/> for instructions.
> > > scripts/Makefile.build:197: recipe for target 'util-linux/mkfs_ext2.o'
> > > failed
> > > make[2]: *** [util-linux/mkfs_ext2.o] Error 1
> > > Makefile:742: recipe for target 'util-linux' failed
> > > make[1]: *** [util-linux] Error 2
> > > make[1]: Leaving directory '/home/administrator/
> > Downloads/buildroot_2017/
> > > buildroot-2017.02.5/output/build/busybox-1.26.2'
> > > package/pkg-generic.mk:216: recipe for target '/home/administrator/
> > > Downloads/buildroot_2017/buildroot-2017.02.5/output/
> > > build/busybox-1.26.2/.stamp_built' failed
> > > make: *** [/home/administrator/Downloads/buildroot_2017/
> > > buildroot-2017.02.5/output/build/busybox-1.26.2/.stamp_built] Error 2
> > >
> > > It would be really helpful is you can provide some insight and possibly a
> > > fix/workaround.
> >
> > Have you done a clean rebuild, i.e., 'make clean; make'? See
> > http://nightly.buildroot.org/manual.html#full-rebuild .
> >
> > baruch
> >
> > > On Thu, Aug 10, 2017 at 8:55 AM, Aseem Sharma <aseem.sharma19@gmail.com>
> > > wrote:
> > >
> > > > Thanks Baruch & Arnout. Will give a try.
> > > >
> > > > Best Regards,
> > > > Aseem
> > > >
> > > > On Wed, Aug 9, 2017 at 10:47 PM, Baruch Siach <baruch@tkos.co.il>
> > wrote:
> > > >
> > > >> Hi Aseem,
> > > >>
> > > >> On Wed, Aug 09, 2017 at 10:03:24PM +0530, Aseem Sharma wrote:
> > > >> > Hello Baruch & Arnout,
> > > >> >
> > > >> > Thanks for your responses.
> > > >> > The board that I have is quite old with limited RAM and Flash.
> > > >> >
> > > >> > Baruch,
> > > >> > Could you please provide more details as to how do I select "iwmmxt"
> > > >> using
> > > >> > menuconfig. As far as I remember, I do not seem to have that option
> > in
> > > >> my
> > > >> > current buildroot release.
> > > >>
> > > >> Go to 'Target options' -> 'Target Architecture Variant', and select
> > > >> 'iwmmxt'
> > > >> (last option).
> > > >>
> > > >> > Also, as per Arnout's response to my query, I should be using ARM
> > little
> > > >> > endian with arm926tARM.
> > > >>
> > > >> As far as I know arm926t code is compatible with iwmmxt, but not the
> > > >> other way
> > > >> around. Look for Sheeva PJ1 at [1]. See also [2].
> > > >>
> > > >> [1] https://en.wikipedia.org/wiki/List_of_ARM_microarchitectures
> > > >>
> > > >> [2] https://en.wikipedia.org/wiki/MMX_(instruction_set)#MMX_in_e
> > > >> mbedded_applications
> > > >>
> > > >> > Are these two options one and the same?
> > > >>
> > > >> I don't think so.
> > > >>
> > > >> baruch
> > > >>
> > > >> > Thanks in advance.
> > > >> >
> > > >> > Best Regards,
> > > >> > Aseem
> > > >> >
> > > >> > Sent via really tiny keyboard. Expect random auto corrects, fat
> > finger
> > > >> > typos and weirdness!!
> > > >> >
> > > >> >
> > > >> > On 09-Aug-2017 21:19, "Baruch Siach" <baruch@tkos.co.il> wrote:
> > > >> >
> > > >> > Hi Aweem,
> > > >> >
> > > >> > On Wed, Aug 09, 2017 at 06:00:55PM +0530, Aseem Sharma wrote:
> > > >> > > I am naive to buildroot & processor world trying to compile
> > > >> > > "buildroot-2017.02.5" for "Marvell ARM Armada 166E processor
> > > >> (compatible
> > > >> > to
> > > >> > > ARMv5TE instruction-set)" based old system. However, I do not
> > > >> understand
> > > >> > > the options to be selected in "make menuconfig" for
> > > >> > > 1. Target options->Target Architecture {think should be ARM -
> > little
> > > >> > endian}
> > > >> > > 2. Target options->Target Architecture variant
> > > >> > >
> > > >> > > Thanks in advance for your help.
> > > >> >
> > > >> > Based on the Armada 16x Datasheet[1], the mainline kernel
> > > >> > arch/arm/mach-mmp/Kconfig (CONFIG_CPU_PXA168) and arch/arm/Kconfig
> > > >> > (CONFIG_IWMMXT), it seems like you need the iwmmxt ARM variant for
> > your
> > > >> > Armada
> > > >> > 166E processor.
> > > >> >
> > > >> > [1] http://www.marvell.com.cn/application-processors/armada-100/
> > > >> > assets/armada_16x_datasheet.pdf

-- 
     http://baruch.siach.name/blog/                  ~. .~   Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
   - baruch at tkos.co.il - tel: +972.52.368.4656, http://www.tkos.co.il -

[Buildroot] Compiling buildroot for Arm "Armada 166E" Target

[Aseem Sharma]

Sure. Can you please give me the exact steps to be carried out.
Also, I tried selecting other gcc versions from menuconfig but the
compilation seems to fail all the time with one issue or the other.

Best Regards,
Aseem

Sent via really tiny keyboard. Expect random auto corrects, fat finger
typos and weirdness!!

On 10-Aug-2017 12:43 PM, "Baruch Siach" <baruch@tkos.co.il> wrote:

Hi Aseem,

On Thu, Aug 10, 2017 at 12:19:33PM +0530, Aseem Sharma wrote:
> Yes Baruch. I tried a couple of times with "make clean" & even "make
> distclean". However, the error is consistent.
> Found a similar issue here: https://gcc.gnu.org/bugzilla/
> show_bug.cgi?id=40836

This issue seems to be fixed since gcc 4.8.

I could not reproduce this ICE on current master with the following minimal
defconfig:

BR2_arm=y
BR2_iwmmxt=y

Can you give it a try?

baruch

> On Thu, Aug 10, 2017 at 12:06 PM, Baruch Siach <baruch@tkos.co.il> wrote:
> > On Thu, Aug 10, 2017 at 11:56:56AM +0530, Aseem Sharma wrote:
> > > *A follow-up question:*
> > > I selected 'iwmmxt' as per Baruch's suggestion and tried to run
"make".
> > > The build seems to be failing with following error message in
> > > "busybox-1.26.2" compilation:
> > >
> > > util-linux/mkfs_ext2.c: In function ?mkfs_ext2_main?:
> > > util-linux/mkfs_ext2.c:715:1: error: insn does not satisfy its
> > constraints:
> > >  }
> > >  ^
> > > (insn 1169 286 287 31 (set (reg:SI 0 r0)
> > >         (reg:SI 80 wr0)) util-linux/mkfs_ext2.c:344 426
> > {*iwmmxt_movsi_insn}
> > >      (nil))
> > > util-linux/mkfs_ext2.c:715:1: internal compiler error: in
> > > reload_cse_simplify_operands, at postreload.c:411
> > > Please submit a full bug report,
> > > with preprocessed source if appropriate.
> > > See <http://bugs.buildroot.net/> for instructions.
> > > scripts/Makefile.build:197: recipe for target 'util-linux/mkfs_ext2.o'
> > > failed
> > > make[2]: *** [util-linux/mkfs_ext2.o] Error 1
> > > Makefile:742: recipe for target 'util-linux' failed
> > > make[1]: *** [util-linux] Error 2
> > > make[1]: Leaving directory '/home/administrator/
> > Downloads/buildroot_2017/
> > > buildroot-2017.02.5/output/build/busybox-1.26.2'
> > > package/pkg-generic.mk:216: recipe for target '/home/administrator/
> > > Downloads/buildroot_2017/buildroot-2017.02.5/output/
> > > build/busybox-1.26.2/.stamp_built' failed
> > > make: *** [/home/administrator/Downloads/buildroot_2017/
> > > buildroot-2017.02.5/output/build/busybox-1.26.2/.stamp_built] Error 2
> > >
> > > It would be really helpful is you can provide some insight and
possibly a
> > > fix/workaround.
> >
> > Have you done a clean rebuild, i.e., 'make clean; make'? See
> > http://nightly.buildroot.org/manual.html#full-rebuild .
> >
> > baruch
> >
> > > On Thu, Aug 10, 2017 at 8:55 AM, Aseem Sharma <
aseem.sharma19@gmail.com>
> > > wrote:
> > >
> > > > Thanks Baruch & Arnout. Will give a try.
> > > >
> > > > Best Regards,
> > > > Aseem
> > > >
> > > > On Wed, Aug 9, 2017 at 10:47 PM, Baruch Siach <baruch@tkos.co.il>
> > wrote:
> > > >
> > > >> Hi Aseem,
> > > >>
> > > >> On Wed, Aug 09, 2017 at 10:03:24PM +0530, Aseem Sharma wrote:
> > > >> > Hello Baruch & Arnout,
> > > >> >
> > > >> > Thanks for your responses.
> > > >> > The board that I have is quite old with limited RAM and Flash.
> > > >> >
> > > >> > Baruch,
> > > >> > Could you please provide more details as to how do I select
"iwmmxt"
> > > >> using
> > > >> > menuconfig. As far as I remember, I do not seem to have that
option
> > in
> > > >> my
> > > >> > current buildroot release.
> > > >>
> > > >> Go to 'Target options' -> 'Target Architecture Variant', and select
> > > >> 'iwmmxt'
> > > >> (last option).
> > > >>
> > > >> > Also, as per Arnout's response to my query, I should be using ARM
> > little
> > > >> > endian with arm926tARM.
> > > >>
> > > >> As far as I know arm926t code is compatible with iwmmxt, but not
the
> > > >> other way
> > > >> around. Look for Sheeva PJ1 at [1]. See also [2].
> > > >>
> > > >> [1] https://en.wikipedia.org/wiki/List_of_ARM_microarchitectures
> > > >>
> > > >> [2] https://en.wikipedia.org/wiki/MMX_(instruction_set)#MMX_in_e
> > > >> mbedded_applications
> > > >>
> > > >> > Are these two options one and the same?
> > > >>
> > > >> I don't think so.
> > > >>
> > > >> baruch
> > > >>
> > > >> > Thanks in advance.
> > > >> >
> > > >> > Best Regards,
> > > >> > Aseem
> > > >> >
> > > >> > Sent via really tiny keyboard. Expect random auto corrects, fat
> > finger
> > > >> > typos and weirdness!!
> > > >> >
> > > >> >
> > > >> > On 09-Aug-2017 21:19, "Baruch Siach" <baruch@tkos.co.il> wrote:
> > > >> >
> > > >> > Hi Aweem,
> > > >> >
> > > >> > On Wed, Aug 09, 2017 at 06:00:55PM +0530, Aseem Sharma wrote:
> > > >> > > I am naive to buildroot & processor world trying to compile
> > > >> > > "buildroot-2017.02.5" for "Marvell ARM Armada 166E processor
> > > >> (compatible
> > > >> > to
> > > >> > > ARMv5TE instruction-set)" based old system. However, I do not
> > > >> understand
> > > >> > > the options to be selected in "make menuconfig" for
> > > >> > > 1. Target options->Target Architecture {think should be ARM -
> > little
> > > >> > endian}
> > > >> > > 2. Target options->Target Architecture variant
> > > >> > >
> > > >> > > Thanks in advance for your help.
> > > >> >
> > > >> > Based on the Armada 16x Datasheet[1], the mainline kernel
> > > >> > arch/arm/mach-mmp/Kconfig (CONFIG_CPU_PXA168) and
arch/arm/Kconfig
> > > >> > (CONFIG_IWMMXT), it seems like you need the iwmmxt ARM variant
for
> > your
> > > >> > Armada
> > > >> > 166E processor.
> > > >> >
> > > >> > [1] http://www.marvell.com.cn/application-processors/armada-100/
> > > >> > assets/armada_16x_datasheet.pdf

--
     http://baruch.siach.name/blog/                  ~. .~   Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
   - baruch at tkos.co.il - tel: +972.52.368.4656, http://www.tkos.co.il -
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20170810/5a5d9528/attachment.html>

[Buildroot] Compiling buildroot for Arm "Armada 166E" Target

[Baruch Siach]

Hi Aseem,

On Thu, Aug 10, 2017 at 12:51:53PM +0530, Aseem Sharma wrote:
> Sure. Can you please give me the exact steps to be carried out.
> Also, I tried selecting other gcc versions from menuconfig but the
> compilation seems to fail all the time with one issue or the other.

Remove your current .config, copy the minimal defconfig below into .config, 
and then do

  make olddefconfig
  make clean
  make

This will automatically select the gcc version which as of current master is 
6.4.0.

baruch

> On 10-Aug-2017 12:43 PM, "Baruch Siach" <baruch@tkos.co.il> wrote:
> 
> On Thu, Aug 10, 2017 at 12:19:33PM +0530, Aseem Sharma wrote:
> > Yes Baruch. I tried a couple of times with "make clean" & even "make
> > distclean". However, the error is consistent.
> > Found a similar issue here: https://gcc.gnu.org/bugzilla/
> > show_bug.cgi?id=40836
> 
> This issue seems to be fixed since gcc 4.8.
> 
> I could not reproduce this ICE on current master with the following minimal
> defconfig:
> 
> BR2_arm=y
> BR2_iwmmxt=y
> 
> Can you give it a try?
> 
> baruch
> 
> > On Thu, Aug 10, 2017 at 12:06 PM, Baruch Siach <baruch@tkos.co.il> wrote:
> > > On Thu, Aug 10, 2017 at 11:56:56AM +0530, Aseem Sharma wrote:
> > > > *A follow-up question:*
> > > > I selected 'iwmmxt' as per Baruch's suggestion and tried to run
> "make".
> > > > The build seems to be failing with following error message in
> > > > "busybox-1.26.2" compilation:
> > > >
> > > > util-linux/mkfs_ext2.c: In function ?mkfs_ext2_main?:
> > > > util-linux/mkfs_ext2.c:715:1: error: insn does not satisfy its
> > > constraints:
> > > >  }
> > > >  ^
> > > > (insn 1169 286 287 31 (set (reg:SI 0 r0)
> > > >         (reg:SI 80 wr0)) util-linux/mkfs_ext2.c:344 426
> > > {*iwmmxt_movsi_insn}
> > > >      (nil))
> > > > util-linux/mkfs_ext2.c:715:1: internal compiler error: in
> > > > reload_cse_simplify_operands, at postreload.c:411
> > > > Please submit a full bug report,
> > > > with preprocessed source if appropriate.
> > > > See <http://bugs.buildroot.net/> for instructions.
> > > > scripts/Makefile.build:197: recipe for target 'util-linux/mkfs_ext2.o'
> > > > failed
> > > > make[2]: *** [util-linux/mkfs_ext2.o] Error 1
> > > > Makefile:742: recipe for target 'util-linux' failed
> > > > make[1]: *** [util-linux] Error 2
> > > > make[1]: Leaving directory '/home/administrator/
> > > Downloads/buildroot_2017/
> > > > buildroot-2017.02.5/output/build/busybox-1.26.2'
> > > > package/pkg-generic.mk:216: recipe for target '/home/administrator/
> > > > Downloads/buildroot_2017/buildroot-2017.02.5/output/
> > > > build/busybox-1.26.2/.stamp_built' failed
> > > > make: *** [/home/administrator/Downloads/buildroot_2017/
> > > > buildroot-2017.02.5/output/build/busybox-1.26.2/.stamp_built] Error 2
> > > >
> > > > It would be really helpful is you can provide some insight and
> possibly a
> > > > fix/workaround.
> > >
> > > Have you done a clean rebuild, i.e., 'make clean; make'? See
> > > http://nightly.buildroot.org/manual.html#full-rebuild .
> > >
> > > baruch
> > >
> > > > On Thu, Aug 10, 2017 at 8:55 AM, Aseem Sharma <
> aseem.sharma19 at gmail.com>
> > > > wrote:
> > > >
> > > > > Thanks Baruch & Arnout. Will give a try.
> > > > >
> > > > > Best Regards,
> > > > > Aseem
> > > > >
> > > > > On Wed, Aug 9, 2017 at 10:47 PM, Baruch Siach <baruch@tkos.co.il>
> > > wrote:
> > > > >
> > > > >> Hi Aseem,
> > > > >>
> > > > >> On Wed, Aug 09, 2017 at 10:03:24PM +0530, Aseem Sharma wrote:
> > > > >> > Hello Baruch & Arnout,
> > > > >> >
> > > > >> > Thanks for your responses.
> > > > >> > The board that I have is quite old with limited RAM and Flash.
> > > > >> >
> > > > >> > Baruch,
> > > > >> > Could you please provide more details as to how do I select
> "iwmmxt"
> > > > >> using
> > > > >> > menuconfig. As far as I remember, I do not seem to have that
> option
> > > in
> > > > >> my
> > > > >> > current buildroot release.
> > > > >>
> > > > >> Go to 'Target options' -> 'Target Architecture Variant', and select
> > > > >> 'iwmmxt'
> > > > >> (last option).
> > > > >>
> > > > >> > Also, as per Arnout's response to my query, I should be using ARM
> > > little
> > > > >> > endian with arm926tARM.
> > > > >>
> > > > >> As far as I know arm926t code is compatible with iwmmxt, but not
> the
> > > > >> other way
> > > > >> around. Look for Sheeva PJ1 at [1]. See also [2].
> > > > >>
> > > > >> [1] https://en.wikipedia.org/wiki/List_of_ARM_microarchitectures
> > > > >>
> > > > >> [2] https://en.wikipedia.org/wiki/MMX_(instruction_set)#MMX_in_e
> > > > >> mbedded_applications
> > > > >>
> > > > >> > Are these two options one and the same?
> > > > >>
> > > > >> I don't think so.
> > > > >>
> > > > >> baruch
> > > > >>
> > > > >> > Thanks in advance.
> > > > >> >
> > > > >> > Best Regards,
> > > > >> > Aseem
> > > > >> >
> > > > >> > Sent via really tiny keyboard. Expect random auto corrects, fat
> > > finger
> > > > >> > typos and weirdness!!
> > > > >> >
> > > > >> >
> > > > >> > On 09-Aug-2017 21:19, "Baruch Siach" <baruch@tkos.co.il> wrote:
> > > > >> >
> > > > >> > Hi Aweem,
> > > > >> >
> > > > >> > On Wed, Aug 09, 2017 at 06:00:55PM +0530, Aseem Sharma wrote:
> > > > >> > > I am naive to buildroot & processor world trying to compile
> > > > >> > > "buildroot-2017.02.5" for "Marvell ARM Armada 166E processor
> > > > >> (compatible
> > > > >> > to
> > > > >> > > ARMv5TE instruction-set)" based old system. However, I do not
> > > > >> understand
> > > > >> > > the options to be selected in "make menuconfig" for
> > > > >> > > 1. Target options->Target Architecture {think should be ARM -
> > > little
> > > > >> > endian}
> > > > >> > > 2. Target options->Target Architecture variant
> > > > >> > >
> > > > >> > > Thanks in advance for your help.
> > > > >> >
> > > > >> > Based on the Armada 16x Datasheet[1], the mainline kernel
> > > > >> > arch/arm/mach-mmp/Kconfig (CONFIG_CPU_PXA168) and
> arch/arm/Kconfig
> > > > >> > (CONFIG_IWMMXT), it seems like you need the iwmmxt ARM variant
> for
> > > your
> > > > >> > Armada
> > > > >> > 166E processor.
> > > > >> >
> > > > >> > [1] http://www.marvell.com.cn/application-processors/armada-100/
> > > > >> > assets/armada_16x_datasheet.pdf
> 
> --
>      http://baruch.siach.name/blog/                  ~. .~   Tk Open Systems
> =}------------------------------------------------ooO--U--Ooo------------{=
>    - baruch at tkos.co.il - tel: +972.52.368.4656, http://www.tkos.co.il -

-- 
     http://baruch.siach.name/blog/                  ~. .~   Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
   - baruch at tkos.co.il - tel: +972.52.368.4656, http://www.tkos.co.il -

[Buildroot] Compiling buildroot for Arm "Armada 166E" Target

[Aseem Sharma]

Where will i find minimal defconfig?
Please note that the issue was orignally observed on latest long term
support release v2017.02.5.
However I would try the steps provided in your last email over Latest
stable release v2017.05.2.
Sorry about too many naive questions.

-Aseem

On Thu, Aug 10, 2017 at 12:58 PM, Baruch Siach <baruch@tkos.co.il> wrote:

> Hi Aseem,
>
> On Thu, Aug 10, 2017 at 12:51:53PM +0530, Aseem Sharma wrote:
> > Sure. Can you please give me the exact steps to be carried out.
> > Also, I tried selecting other gcc versions from menuconfig but the
> > compilation seems to fail all the time with one issue or the other.
>
> Remove your current .config, copy the minimal defconfig below into .config,
> and then do
>
>   make olddefconfig
>   make clean
>   make
>
> This will automatically select the gcc version which as of current master
> is
> 6.4.0.
>
> baruch
>
> > On 10-Aug-2017 12:43 PM, "Baruch Siach" <baruch@tkos.co.il> wrote:
> >
> > On Thu, Aug 10, 2017 at 12:19:33PM +0530, Aseem Sharma wrote:
> > > Yes Baruch. I tried a couple of times with "make clean" & even "make
> > > distclean". However, the error is consistent.
> > > Found a similar issue here: https://gcc.gnu.org/bugzilla/
> > > show_bug.cgi?id=40836
> >
> > This issue seems to be fixed since gcc 4.8.
> >
> > I could not reproduce this ICE on current master with the following
> minimal
> > defconfig:
> >
> > BR2_arm=y
> > BR2_iwmmxt=y
> >
> > Can you give it a try?
> >
> > baruch
> >
> > > On Thu, Aug 10, 2017 at 12:06 PM, Baruch Siach <baruch@tkos.co.il>
> wrote:
> > > > On Thu, Aug 10, 2017 at 11:56:56AM +0530, Aseem Sharma wrote:
> > > > > *A follow-up question:*
> > > > > I selected 'iwmmxt' as per Baruch's suggestion and tried to run
> > "make".
> > > > > The build seems to be failing with following error message in
> > > > > "busybox-1.26.2" compilation:
> > > > >
> > > > > util-linux/mkfs_ext2.c: In function ?mkfs_ext2_main?:
> > > > > util-linux/mkfs_ext2.c:715:1: error: insn does not satisfy its
> > > > constraints:
> > > > >  }
> > > > >  ^
> > > > > (insn 1169 286 287 31 (set (reg:SI 0 r0)
> > > > >         (reg:SI 80 wr0)) util-linux/mkfs_ext2.c:344 426
> > > > {*iwmmxt_movsi_insn}
> > > > >      (nil))
> > > > > util-linux/mkfs_ext2.c:715:1: internal compiler error: in
> > > > > reload_cse_simplify_operands, at postreload.c:411
> > > > > Please submit a full bug report,
> > > > > with preprocessed source if appropriate.
> > > > > See <http://bugs.buildroot.net/> for instructions.
> > > > > scripts/Makefile.build:197: recipe for target
> 'util-linux/mkfs_ext2.o'
> > > > > failed
> > > > > make[2]: *** [util-linux/mkfs_ext2.o] Error 1
> > > > > Makefile:742: recipe for target 'util-linux' failed
> > > > > make[1]: *** [util-linux] Error 2
> > > > > make[1]: Leaving directory '/home/administrator/
> > > > Downloads/buildroot_2017/
> > > > > buildroot-2017.02.5/output/build/busybox-1.26.2'
> > > > > package/pkg-generic.mk:216: recipe for target
> '/home/administrator/
> > > > > Downloads/buildroot_2017/buildroot-2017.02.5/output/
> > > > > build/busybox-1.26.2/.stamp_built' failed
> > > > > make: *** [/home/administrator/Downloads/buildroot_2017/
> > > > > buildroot-2017.02.5/output/build/busybox-1.26.2/.stamp_built]
> Error 2
> > > > >
> > > > > It would be really helpful is you can provide some insight and
> > possibly a
> > > > > fix/workaround.
> > > >
> > > > Have you done a clean rebuild, i.e., 'make clean; make'? See
> > > > http://nightly.buildroot.org/manual.html#full-rebuild .
> > > >
> > > > baruch
> > > >
> > > > > On Thu, Aug 10, 2017 at 8:55 AM, Aseem Sharma <
> > aseem.sharma19 at gmail.com>
> > > > > wrote:
> > > > >
> > > > > > Thanks Baruch & Arnout. Will give a try.
> > > > > >
> > > > > > Best Regards,
> > > > > > Aseem
> > > > > >
> > > > > > On Wed, Aug 9, 2017 at 10:47 PM, Baruch Siach <baruch@tkos.co.il
> >
> > > > wrote:
> > > > > >
> > > > > >> Hi Aseem,
> > > > > >>
> > > > > >> On Wed, Aug 09, 2017 at 10:03:24PM +0530, Aseem Sharma wrote:
> > > > > >> > Hello Baruch & Arnout,
> > > > > >> >
> > > > > >> > Thanks for your responses.
> > > > > >> > The board that I have is quite old with limited RAM and Flash.
> > > > > >> >
> > > > > >> > Baruch,
> > > > > >> > Could you please provide more details as to how do I select
> > "iwmmxt"
> > > > > >> using
> > > > > >> > menuconfig. As far as I remember, I do not seem to have that
> > option
> > > > in
> > > > > >> my
> > > > > >> > current buildroot release.
> > > > > >>
> > > > > >> Go to 'Target options' -> 'Target Architecture Variant', and
> select
> > > > > >> 'iwmmxt'
> > > > > >> (last option).
> > > > > >>
> > > > > >> > Also, as per Arnout's response to my query, I should be using
> ARM
> > > > little
> > > > > >> > endian with arm926tARM.
> > > > > >>
> > > > > >> As far as I know arm926t code is compatible with iwmmxt, but not
> > the
> > > > > >> other way
> > > > > >> around. Look for Sheeva PJ1 at [1]. See also [2].
> > > > > >>
> > > > > >> [1] https://en.wikipedia.org/wiki/
> List_of_ARM_microarchitectures
> > > > > >>
> > > > > >> [2] https://en.wikipedia.org/wiki/
> MMX_(instruction_set)#MMX_in_e
> > > > > >> mbedded_applications
> > > > > >>
> > > > > >> > Are these two options one and the same?
> > > > > >>
> > > > > >> I don't think so.
> > > > > >>
> > > > > >> baruch
> > > > > >>
> > > > > >> > Thanks in advance.
> > > > > >> >
> > > > > >> > Best Regards,
> > > > > >> > Aseem
> > > > > >> >
> > > > > >> > Sent via really tiny keyboard. Expect random auto corrects,
> fat
> > > > finger
> > > > > >> > typos and weirdness!!
> > > > > >> >
> > > > > >> >
> > > > > >> > On 09-Aug-2017 21:19, "Baruch Siach" <baruch@tkos.co.il>
> wrote:
> > > > > >> >
> > > > > >> > Hi Aweem,
> > > > > >> >
> > > > > >> > On Wed, Aug 09, 2017 at 06:00:55PM +0530, Aseem Sharma wrote:
> > > > > >> > > I am naive to buildroot & processor world trying to compile
> > > > > >> > > "buildroot-2017.02.5" for "Marvell ARM Armada 166E processor
> > > > > >> (compatible
> > > > > >> > to
> > > > > >> > > ARMv5TE instruction-set)" based old system. However, I do
> not
> > > > > >> understand
> > > > > >> > > the options to be selected in "make menuconfig" for
> > > > > >> > > 1. Target options->Target Architecture {think should be ARM
> -
> > > > little
> > > > > >> > endian}
> > > > > >> > > 2. Target options->Target Architecture variant
> > > > > >> > >
> > > > > >> > > Thanks in advance for your help.
> > > > > >> >
> > > > > >> > Based on the Armada 16x Datasheet[1], the mainline kernel
> > > > > >> > arch/arm/mach-mmp/Kconfig (CONFIG_CPU_PXA168) and
> > arch/arm/Kconfig
> > > > > >> > (CONFIG_IWMMXT), it seems like you need the iwmmxt ARM variant
> > for
> > > > your
> > > > > >> > Armada
> > > > > >> > 166E processor.
> > > > > >> >
> > > > > >> > [1] http://www.marvell.com.cn/application-processors/armada-
> 100/
> > > > > >> > assets/armada_16x_datasheet.pdf
> >
> > --
> >      http://baruch.siach.name/blog/                  ~. .~   Tk Open
> Systems
> > =}------------------------------------------------ooO--U--
> Ooo------------{=
> >    - baruch at tkos.co.il - tel: +972.52.368.4656, http://www.tkos.co.il -
>
> --
>      http://baruch.siach.name/blog/                  ~. .~   Tk Open
> Systems
> =}------------------------------------------------ooO--U--
> Ooo------------{=
>    - baruch at tkos.co.il - tel: +972.52.368.4656, http://www.tkos.co.il -
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20170810/f94180fd/attachment.html>

[Buildroot] Compiling buildroot for Arm "Armada 166E" Target

[Baruch Siach]

Hi Aseem,

On Thu, Aug 10, 2017 at 01:39:18PM +0530, Aseem Sharma wrote:
> Where will i find minimal defconfig?

The minimal defconfig is in my quoted message below. Here it is again:

BR2_arm=y
BR2_iwmmxt=y

> Please note that the issue was orignally observed on latest long term
> support release v2017.02.5.
> However I would try the steps provided in your last email over Latest
> stable release v2017.05.2.
> Sorry about too many naive questions.

baruch

> On Thu, Aug 10, 2017 at 12:58 PM, Baruch Siach <baruch@tkos.co.il> wrote:
> > On Thu, Aug 10, 2017 at 12:51:53PM +0530, Aseem Sharma wrote:
> > > Sure. Can you please give me the exact steps to be carried out.
> > > Also, I tried selecting other gcc versions from menuconfig but the
> > > compilation seems to fail all the time with one issue or the other.
> >
> > Remove your current .config, copy the minimal defconfig below into .config,
> > and then do
> >
> >   make olddefconfig
> >   make clean
> >   make
> >
> > This will automatically select the gcc version which as of current master
> > is
> > 6.4.0.
> >
> > baruch
> >
> > > On 10-Aug-2017 12:43 PM, "Baruch Siach" <baruch@tkos.co.il> wrote:
> > >
> > > On Thu, Aug 10, 2017 at 12:19:33PM +0530, Aseem Sharma wrote:
> > > > Yes Baruch. I tried a couple of times with "make clean" & even "make
> > > > distclean". However, the error is consistent.
> > > > Found a similar issue here: https://gcc.gnu.org/bugzilla/
> > > > show_bug.cgi?id=40836
> > >
> > > This issue seems to be fixed since gcc 4.8.
> > >
> > > I could not reproduce this ICE on current master with the following
> > minimal
> > > defconfig:
> > >
> > > BR2_arm=y
> > > BR2_iwmmxt=y
> > >
> > > Can you give it a try?
> > >
> > > baruch
> > >
> > > > On Thu, Aug 10, 2017 at 12:06 PM, Baruch Siach <baruch@tkos.co.il>
> > wrote:
> > > > > On Thu, Aug 10, 2017 at 11:56:56AM +0530, Aseem Sharma wrote:
> > > > > > *A follow-up question:*
> > > > > > I selected 'iwmmxt' as per Baruch's suggestion and tried to run
> > > "make".
> > > > > > The build seems to be failing with following error message in
> > > > > > "busybox-1.26.2" compilation:
> > > > > >
> > > > > > util-linux/mkfs_ext2.c: In function ?mkfs_ext2_main?:
> > > > > > util-linux/mkfs_ext2.c:715:1: error: insn does not satisfy its
> > > > > constraints:
> > > > > >  }
> > > > > >  ^
> > > > > > (insn 1169 286 287 31 (set (reg:SI 0 r0)
> > > > > >         (reg:SI 80 wr0)) util-linux/mkfs_ext2.c:344 426
> > > > > {*iwmmxt_movsi_insn}
> > > > > >      (nil))
> > > > > > util-linux/mkfs_ext2.c:715:1: internal compiler error: in
> > > > > > reload_cse_simplify_operands, at postreload.c:411
> > > > > > Please submit a full bug report,
> > > > > > with preprocessed source if appropriate.
> > > > > > See <http://bugs.buildroot.net/> for instructions.
> > > > > > scripts/Makefile.build:197: recipe for target
> > 'util-linux/mkfs_ext2.o'
> > > > > > failed
> > > > > > make[2]: *** [util-linux/mkfs_ext2.o] Error 1
> > > > > > Makefile:742: recipe for target 'util-linux' failed
> > > > > > make[1]: *** [util-linux] Error 2
> > > > > > make[1]: Leaving directory '/home/administrator/
> > > > > Downloads/buildroot_2017/
> > > > > > buildroot-2017.02.5/output/build/busybox-1.26.2'
> > > > > > package/pkg-generic.mk:216: recipe for target
> > '/home/administrator/
> > > > > > Downloads/buildroot_2017/buildroot-2017.02.5/output/
> > > > > > build/busybox-1.26.2/.stamp_built' failed
> > > > > > make: *** [/home/administrator/Downloads/buildroot_2017/
> > > > > > buildroot-2017.02.5/output/build/busybox-1.26.2/.stamp_built]
> > Error 2
> > > > > >
> > > > > > It would be really helpful is you can provide some insight and
> > > possibly a
> > > > > > fix/workaround.
> > > > >
> > > > > Have you done a clean rebuild, i.e., 'make clean; make'? See
> > > > > http://nightly.buildroot.org/manual.html#full-rebuild .
> > > > >
> > > > > baruch
> > > > >
> > > > > > On Thu, Aug 10, 2017 at 8:55 AM, Aseem Sharma <
> > > aseem.sharma19 at gmail.com>
> > > > > > wrote:
> > > > > >
> > > > > > > Thanks Baruch & Arnout. Will give a try.
> > > > > > >
> > > > > > > Best Regards,
> > > > > > > Aseem
> > > > > > >
> > > > > > > On Wed, Aug 9, 2017 at 10:47 PM, Baruch Siach <baruch@tkos.co.il
> > >
> > > > > wrote:
> > > > > > >
> > > > > > >> Hi Aseem,
> > > > > > >>
> > > > > > >> On Wed, Aug 09, 2017 at 10:03:24PM +0530, Aseem Sharma wrote:
> > > > > > >> > Hello Baruch & Arnout,
> > > > > > >> >
> > > > > > >> > Thanks for your responses.
> > > > > > >> > The board that I have is quite old with limited RAM and Flash.
> > > > > > >> >
> > > > > > >> > Baruch,
> > > > > > >> > Could you please provide more details as to how do I select
> > > "iwmmxt"
> > > > > > >> using
> > > > > > >> > menuconfig. As far as I remember, I do not seem to have that
> > > option
> > > > > in
> > > > > > >> my
> > > > > > >> > current buildroot release.
> > > > > > >>
> > > > > > >> Go to 'Target options' -> 'Target Architecture Variant', and
> > select
> > > > > > >> 'iwmmxt'
> > > > > > >> (last option).
> > > > > > >>
> > > > > > >> > Also, as per Arnout's response to my query, I should be using
> > ARM
> > > > > little
> > > > > > >> > endian with arm926tARM.
> > > > > > >>
> > > > > > >> As far as I know arm926t code is compatible with iwmmxt, but not
> > > the
> > > > > > >> other way
> > > > > > >> around. Look for Sheeva PJ1 at [1]. See also [2].
> > > > > > >>
> > > > > > >> [1] https://en.wikipedia.org/wiki/
> > List_of_ARM_microarchitectures
> > > > > > >>
> > > > > > >> [2] https://en.wikipedia.org/wiki/
> > MMX_(instruction_set)#MMX_in_e
> > > > > > >> mbedded_applications
> > > > > > >>
> > > > > > >> > Are these two options one and the same?
> > > > > > >>
> > > > > > >> I don't think so.
> > > > > > >>
> > > > > > >> baruch
> > > > > > >>
> > > > > > >> > Thanks in advance.
> > > > > > >> >
> > > > > > >> > Best Regards,
> > > > > > >> > Aseem
> > > > > > >> >
> > > > > > >> > Sent via really tiny keyboard. Expect random auto corrects,
> > fat
> > > > > finger
> > > > > > >> > typos and weirdness!!
> > > > > > >> >
> > > > > > >> >
> > > > > > >> > On 09-Aug-2017 21:19, "Baruch Siach" <baruch@tkos.co.il>
> > wrote:
> > > > > > >> >
> > > > > > >> > Hi Aweem,
> > > > > > >> >
> > > > > > >> > On Wed, Aug 09, 2017 at 06:00:55PM +0530, Aseem Sharma wrote:
> > > > > > >> > > I am naive to buildroot & processor world trying to compile
> > > > > > >> > > "buildroot-2017.02.5" for "Marvell ARM Armada 166E processor
> > > > > > >> (compatible
> > > > > > >> > to
> > > > > > >> > > ARMv5TE instruction-set)" based old system. However, I do
> > not
> > > > > > >> understand
> > > > > > >> > > the options to be selected in "make menuconfig" for
> > > > > > >> > > 1. Target options->Target Architecture {think should be ARM
> > -
> > > > > little
> > > > > > >> > endian}
> > > > > > >> > > 2. Target options->Target Architecture variant
> > > > > > >> > >
> > > > > > >> > > Thanks in advance for your help.
> > > > > > >> >
> > > > > > >> > Based on the Armada 16x Datasheet[1], the mainline kernel
> > > > > > >> > arch/arm/mach-mmp/Kconfig (CONFIG_CPU_PXA168) and
> > > arch/arm/Kconfig
> > > > > > >> > (CONFIG_IWMMXT), it seems like you need the iwmmxt ARM variant
> > > for
> > > > > your
> > > > > > >> > Armada
> > > > > > >> > 166E processor.
> > > > > > >> >
> > > > > > >> > [1] http://www.marvell.com.cn/application-processors/armada-
> > 100/
> > > > > > >> > assets/armada_16x_datasheet.pdf

-- 
     http://baruch.siach.name/blog/                  ~. .~   Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
   - baruch at tkos.co.il - tel: +972.52.368.4656, http://www.tkos.co.il -

[Buildroot] Compiling buildroot for Arm "Armada 166E" Target

[Aseem Sharma]

Another information that I may have missed is that I am currently using
Ubuntu 16.4 system, i686 arch to build source for "iwmmxt"

-Aseem

On Thu, Aug 10, 2017 at 1:39 PM, Aseem Sharma <aseem.sharma19@gmail.com>
wrote:

> Where will i find minimal defconfig?
> Please note that the issue was orignally observed on latest long term
> support release v2017.02.5.
> However I would try the steps provided in your last email over Latest
> stable release v2017.05.2.
> Sorry about too many naive questions.
>
> -Aseem
>
> On Thu, Aug 10, 2017 at 12:58 PM, Baruch Siach <baruch@tkos.co.il> wrote:
>
>> Hi Aseem,
>>
>> On Thu, Aug 10, 2017 at 12:51:53PM +0530, Aseem Sharma wrote:
>> > Sure. Can you please give me the exact steps to be carried out.
>> > Also, I tried selecting other gcc versions from menuconfig but the
>> > compilation seems to fail all the time with one issue or the other.
>>
>> Remove your current .config, copy the minimal defconfig below into
>> .config,
>> and then do
>>
>>   make olddefconfig
>>   make clean
>>   make
>>
>> This will automatically select the gcc version which as of current master
>> is
>> 6.4.0.
>>
>> baruch
>>
>> > On 10-Aug-2017 12:43 PM, "Baruch Siach" <baruch@tkos.co.il> wrote:
>> >
>> > On Thu, Aug 10, 2017 at 12:19:33PM +0530, Aseem Sharma wrote:
>> > > Yes Baruch. I tried a couple of times with "make clean" & even "make
>> > > distclean". However, the error is consistent.
>> > > Found a similar issue here: https://gcc.gnu.org/bugzilla/
>> > > show_bug.cgi?id=40836
>> >
>> > This issue seems to be fixed since gcc 4.8.
>> >
>> > I could not reproduce this ICE on current master with the following
>> minimal
>> > defconfig:
>> >
>> > BR2_arm=y
>> > BR2_iwmmxt=y
>> >
>> > Can you give it a try?
>> >
>> > baruch
>> >
>> > > On Thu, Aug 10, 2017 at 12:06 PM, Baruch Siach <baruch@tkos.co.il>
>> wrote:
>> > > > On Thu, Aug 10, 2017 at 11:56:56AM +0530, Aseem Sharma wrote:
>> > > > > *A follow-up question:*
>> > > > > I selected 'iwmmxt' as per Baruch's suggestion and tried to run
>> > "make".
>> > > > > The build seems to be failing with following error message in
>> > > > > "busybox-1.26.2" compilation:
>> > > > >
>> > > > > util-linux/mkfs_ext2.c: In function ?mkfs_ext2_main?:
>> > > > > util-linux/mkfs_ext2.c:715:1: error: insn does not satisfy its
>> > > > constraints:
>> > > > >  }
>> > > > >  ^
>> > > > > (insn 1169 286 287 31 (set (reg:SI 0 r0)
>> > > > >         (reg:SI 80 wr0)) util-linux/mkfs_ext2.c:344 426
>> > > > {*iwmmxt_movsi_insn}
>> > > > >      (nil))
>> > > > > util-linux/mkfs_ext2.c:715:1: internal compiler error: in
>> > > > > reload_cse_simplify_operands, at postreload.c:411
>> > > > > Please submit a full bug report,
>> > > > > with preprocessed source if appropriate.
>> > > > > See <http://bugs.buildroot.net/> for instructions.
>> > > > > scripts/Makefile.build:197: recipe for target
>> 'util-linux/mkfs_ext2.o'
>> > > > > failed
>> > > > > make[2]: *** [util-linux/mkfs_ext2.o] Error 1
>> > > > > Makefile:742: recipe for target 'util-linux' failed
>> > > > > make[1]: *** [util-linux] Error 2
>> > > > > make[1]: Leaving directory '/home/administrator/
>> > > > Downloads/buildroot_2017/
>> > > > > buildroot-2017.02.5/output/build/busybox-1.26.2'
>> > > > > package/pkg-generic.mk:216: recipe for target
>> '/home/administrator/
>> > > > > Downloads/buildroot_2017/buildroot-2017.02.5/output/
>> > > > > build/busybox-1.26.2/.stamp_built' failed
>> > > > > make: *** [/home/administrator/Downloads/buildroot_2017/
>> > > > > buildroot-2017.02.5/output/build/busybox-1.26.2/.stamp_built]
>> Error 2
>> > > > >
>> > > > > It would be really helpful is you can provide some insight and
>> > possibly a
>> > > > > fix/workaround.
>> > > >
>> > > > Have you done a clean rebuild, i.e., 'make clean; make'? See
>> > > > http://nightly.buildroot.org/manual.html#full-rebuild .
>> > > >
>> > > > baruch
>> > > >
>> > > > > On Thu, Aug 10, 2017 at 8:55 AM, Aseem Sharma <
>> > aseem.sharma19 at gmail.com>
>> > > > > wrote:
>> > > > >
>> > > > > > Thanks Baruch & Arnout. Will give a try.
>> > > > > >
>> > > > > > Best Regards,
>> > > > > > Aseem
>> > > > > >
>> > > > > > On Wed, Aug 9, 2017 at 10:47 PM, Baruch Siach <
>> baruch at tkos.co.il>
>> > > > wrote:
>> > > > > >
>> > > > > >> Hi Aseem,
>> > > > > >>
>> > > > > >> On Wed, Aug 09, 2017 at 10:03:24PM +0530, Aseem Sharma wrote:
>> > > > > >> > Hello Baruch & Arnout,
>> > > > > >> >
>> > > > > >> > Thanks for your responses.
>> > > > > >> > The board that I have is quite old with limited RAM and
>> Flash.
>> > > > > >> >
>> > > > > >> > Baruch,
>> > > > > >> > Could you please provide more details as to how do I select
>> > "iwmmxt"
>> > > > > >> using
>> > > > > >> > menuconfig. As far as I remember, I do not seem to have that
>> > option
>> > > > in
>> > > > > >> my
>> > > > > >> > current buildroot release.
>> > > > > >>
>> > > > > >> Go to 'Target options' -> 'Target Architecture Variant', and
>> select
>> > > > > >> 'iwmmxt'
>> > > > > >> (last option).
>> > > > > >>
>> > > > > >> > Also, as per Arnout's response to my query, I should be
>> using ARM
>> > > > little
>> > > > > >> > endian with arm926tARM.
>> > > > > >>
>> > > > > >> As far as I know arm926t code is compatible with iwmmxt, but
>> not
>> > the
>> > > > > >> other way
>> > > > > >> around. Look for Sheeva PJ1 at [1]. See also [2].
>> > > > > >>
>> > > > > >> [1] https://en.wikipedia.org/wiki/
>> List_of_ARM_microarchitectures
>> > > > > >>
>> > > > > >> [2] https://en.wikipedia.org/wiki/
>> MMX_(instruction_set)#MMX_in_e
>> > > > > >> mbedded_applications
>> > > > > >>
>> > > > > >> > Are these two options one and the same?
>> > > > > >>
>> > > > > >> I don't think so.
>> > > > > >>
>> > > > > >> baruch
>> > > > > >>
>> > > > > >> > Thanks in advance.
>> > > > > >> >
>> > > > > >> > Best Regards,
>> > > > > >> > Aseem
>> > > > > >> >
>> > > > > >> > Sent via really tiny keyboard. Expect random auto corrects,
>> fat
>> > > > finger
>> > > > > >> > typos and weirdness!!
>> > > > > >> >
>> > > > > >> >
>> > > > > >> > On 09-Aug-2017 21:19, "Baruch Siach" <baruch@tkos.co.il>
>> wrote:
>> > > > > >> >
>> > > > > >> > Hi Aweem,
>> > > > > >> >
>> > > > > >> > On Wed, Aug 09, 2017 at 06:00:55PM +0530, Aseem Sharma wrote:
>> > > > > >> > > I am naive to buildroot & processor world trying to compile
>> > > > > >> > > "buildroot-2017.02.5" for "Marvell ARM Armada 166E
>> processor
>> > > > > >> (compatible
>> > > > > >> > to
>> > > > > >> > > ARMv5TE instruction-set)" based old system. However, I do
>> not
>> > > > > >> understand
>> > > > > >> > > the options to be selected in "make menuconfig" for
>> > > > > >> > > 1. Target options->Target Architecture {think should be
>> ARM -
>> > > > little
>> > > > > >> > endian}
>> > > > > >> > > 2. Target options->Target Architecture variant
>> > > > > >> > >
>> > > > > >> > > Thanks in advance for your help.
>> > > > > >> >
>> > > > > >> > Based on the Armada 16x Datasheet[1], the mainline kernel
>> > > > > >> > arch/arm/mach-mmp/Kconfig (CONFIG_CPU_PXA168) and
>> > arch/arm/Kconfig
>> > > > > >> > (CONFIG_IWMMXT), it seems like you need the iwmmxt ARM
>> variant
>> > for
>> > > > your
>> > > > > >> > Armada
>> > > > > >> > 166E processor.
>> > > > > >> >
>> > > > > >> > [1] http://www.marvell.com.cn/appl
>> ication-processors/armada-100/
>> > > > > >> > assets/armada_16x_datasheet.pdf
>> >
>> > --
>> >      http://baruch.siach.name/blog/                  ~. .~   Tk Open
>> Systems
>> > =}------------------------------------------------ooO--U--Oo
>> o------------{=
>> >    - baruch at tkos.co.il - tel: +972.52.368.4656, http://www.tkos.co.il -
>>
>> --
>>      http://baruch.siach.name/blog/                  ~. .~   Tk Open
>> Systems
>> =}------------------------------------------------ooO--U--Oo
>> o------------{=
>>    - baruch at tkos.co.il - tel: +972.52.368.4656, http://www.tkos.co.il -
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20170810/2c538f8d/attachment.html>

[Buildroot] Compiling buildroot for Arm "Armada 166E" Target

[Baruch Siach]

Hi Aseem,

On Thu, Aug 10, 2017 at 01:44:10PM +0530, Aseem Sharma wrote:
> Another information that I may have missed is that I am currently using
> Ubuntu 16.4 system, i686 arch to build source for "iwmmxt"

Buildroot is all about cross compiling. Your target architecture is usually 
not the same as your host one.

baruch

> On Thu, Aug 10, 2017 at 1:39 PM, Aseem Sharma <aseem.sharma19@gmail.com>
> wrote:
> > Where will i find minimal defconfig?
> > Please note that the issue was orignally observed on latest long term
> > support release v2017.02.5.
> > However I would try the steps provided in your last email over Latest
> > stable release v2017.05.2.
> > Sorry about too many naive questions.
> >
> > -Aseem
> >
> > On Thu, Aug 10, 2017 at 12:58 PM, Baruch Siach <baruch@tkos.co.il> wrote:
> >
> >> Hi Aseem,
> >>
> >> On Thu, Aug 10, 2017 at 12:51:53PM +0530, Aseem Sharma wrote:
> >> > Sure. Can you please give me the exact steps to be carried out.
> >> > Also, I tried selecting other gcc versions from menuconfig but the
> >> > compilation seems to fail all the time with one issue or the other.
> >>
> >> Remove your current .config, copy the minimal defconfig below into
> >> .config,
> >> and then do
> >>
> >>   make olddefconfig
> >>   make clean
> >>   make
> >>
> >> This will automatically select the gcc version which as of current master
> >> is 6.4.0.
> >>
> >> baruch
> >>
> >> > On 10-Aug-2017 12:43 PM, "Baruch Siach" <baruch@tkos.co.il> wrote:
> >> >
> >> > On Thu, Aug 10, 2017 at 12:19:33PM +0530, Aseem Sharma wrote:
> >> > > Yes Baruch. I tried a couple of times with "make clean" & even "make
> >> > > distclean". However, the error is consistent.
> >> > > Found a similar issue here: https://gcc.gnu.org/bugzilla/
> >> > > show_bug.cgi?id=40836
> >> >
> >> > This issue seems to be fixed since gcc 4.8.
> >> >
> >> > I could not reproduce this ICE on current master with the following
> >> minimal
> >> > defconfig:
> >> >
> >> > BR2_arm=y
> >> > BR2_iwmmxt=y
> >> >
> >> > Can you give it a try?
> >> >
> >> > baruch
> >> >
> >> > > On Thu, Aug 10, 2017 at 12:06 PM, Baruch Siach <baruch@tkos.co.il>
> >> wrote:
> >> > > > On Thu, Aug 10, 2017 at 11:56:56AM +0530, Aseem Sharma wrote:
> >> > > > > *A follow-up question:*
> >> > > > > I selected 'iwmmxt' as per Baruch's suggestion and tried to run
> >> > "make".
> >> > > > > The build seems to be failing with following error message in
> >> > > > > "busybox-1.26.2" compilation:
> >> > > > >
> >> > > > > util-linux/mkfs_ext2.c: In function ?mkfs_ext2_main?:
> >> > > > > util-linux/mkfs_ext2.c:715:1: error: insn does not satisfy its
> >> > > > constraints:
> >> > > > >  }
> >> > > > >  ^
> >> > > > > (insn 1169 286 287 31 (set (reg:SI 0 r0)
> >> > > > >         (reg:SI 80 wr0)) util-linux/mkfs_ext2.c:344 426
> >> > > > {*iwmmxt_movsi_insn}
> >> > > > >      (nil))
> >> > > > > util-linux/mkfs_ext2.c:715:1: internal compiler error: in
> >> > > > > reload_cse_simplify_operands, at postreload.c:411
> >> > > > > Please submit a full bug report,
> >> > > > > with preprocessed source if appropriate.
> >> > > > > See <http://bugs.buildroot.net/> for instructions.
> >> > > > > scripts/Makefile.build:197: recipe for target
> >> 'util-linux/mkfs_ext2.o'
> >> > > > > failed
> >> > > > > make[2]: *** [util-linux/mkfs_ext2.o] Error 1
> >> > > > > Makefile:742: recipe for target 'util-linux' failed
> >> > > > > make[1]: *** [util-linux] Error 2
> >> > > > > make[1]: Leaving directory '/home/administrator/
> >> > > > Downloads/buildroot_2017/
> >> > > > > buildroot-2017.02.5/output/build/busybox-1.26.2'
> >> > > > > package/pkg-generic.mk:216: recipe for target
> >> '/home/administrator/
> >> > > > > Downloads/buildroot_2017/buildroot-2017.02.5/output/
> >> > > > > build/busybox-1.26.2/.stamp_built' failed
> >> > > > > make: *** [/home/administrator/Downloads/buildroot_2017/
> >> > > > > buildroot-2017.02.5/output/build/busybox-1.26.2/.stamp_built]
> >> Error 2
> >> > > > >
> >> > > > > It would be really helpful is you can provide some insight and
> >> > possibly a
> >> > > > > fix/workaround.

-- 
     http://baruch.siach.name/blog/                  ~. .~   Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
   - baruch at tkos.co.il - tel: +972.52.368.4656, http://www.tkos.co.il -

[Buildroot] Compiling buildroot for Arm "Armada 166E" Target

[Aseem Sharma]

Hello Baruch,

The build passes with minimal defconfig on Latest stable release v2017.05.2
and also on latest long term support release v2017.02.5.
So the issue seems to be with my config settings. Is there any workarounds
to fix/avoid the issue?

Thanks & Regards,
Aseem



On Thu, Aug 10, 2017 at 1:44 PM, Aseem Sharma <aseem.sharma19@gmail.com>
wrote:

> Another information that I may have missed is that I am currently using
> Ubuntu 16.4 system, i686 arch to build source for "iwmmxt"
>
> -Aseem
>
> On Thu, Aug 10, 2017 at 1:39 PM, Aseem Sharma <aseem.sharma19@gmail.com>
> wrote:
>
>> Where will i find minimal defconfig?
>> Please note that the issue was orignally observed on latest long term
>> support release v2017.02.5.
>> However I would try the steps provided in your last email over Latest
>> stable release v2017.05.2.
>> Sorry about too many naive questions.
>>
>> -Aseem
>>
>> On Thu, Aug 10, 2017 at 12:58 PM, Baruch Siach <baruch@tkos.co.il> wrote:
>>
>>> Hi Aseem,
>>>
>>> On Thu, Aug 10, 2017 at 12:51:53PM +0530, Aseem Sharma wrote:
>>> > Sure. Can you please give me the exact steps to be carried out.
>>> > Also, I tried selecting other gcc versions from menuconfig but the
>>> > compilation seems to fail all the time with one issue or the other.
>>>
>>> Remove your current .config, copy the minimal defconfig below into
>>> .config,
>>> and then do
>>>
>>>   make olddefconfig
>>>   make clean
>>>   make
>>>
>>> This will automatically select the gcc version which as of current
>>> master is
>>> 6.4.0.
>>>
>>> baruch
>>>
>>> > On 10-Aug-2017 12:43 PM, "Baruch Siach" <baruch@tkos.co.il> wrote:
>>> >
>>> > On Thu, Aug 10, 2017 at 12:19:33PM +0530, Aseem Sharma wrote:
>>> > > Yes Baruch. I tried a couple of times with "make clean" & even "make
>>> > > distclean". However, the error is consistent.
>>> > > Found a similar issue here: https://gcc.gnu.org/bugzilla/
>>> > > show_bug.cgi?id=40836
>>> >
>>> > This issue seems to be fixed since gcc 4.8.
>>> >
>>> > I could not reproduce this ICE on current master with the following
>>> minimal
>>> > defconfig:
>>> >
>>> > BR2_arm=y
>>> > BR2_iwmmxt=y
>>> >
>>> > Can you give it a try?
>>> >
>>> > baruch
>>> >
>>> > > On Thu, Aug 10, 2017 at 12:06 PM, Baruch Siach <baruch@tkos.co.il>
>>> wrote:
>>> > > > On Thu, Aug 10, 2017 at 11:56:56AM +0530, Aseem Sharma wrote:
>>> > > > > *A follow-up question:*
>>> > > > > I selected 'iwmmxt' as per Baruch's suggestion and tried to run
>>> > "make".
>>> > > > > The build seems to be failing with following error message in
>>> > > > > "busybox-1.26.2" compilation:
>>> > > > >
>>> > > > > util-linux/mkfs_ext2.c: In function ?mkfs_ext2_main?:
>>> > > > > util-linux/mkfs_ext2.c:715:1: error: insn does not satisfy its
>>> > > > constraints:
>>> > > > >  }
>>> > > > >  ^
>>> > > > > (insn 1169 286 287 31 (set (reg:SI 0 r0)
>>> > > > >         (reg:SI 80 wr0)) util-linux/mkfs_ext2.c:344 426
>>> > > > {*iwmmxt_movsi_insn}
>>> > > > >      (nil))
>>> > > > > util-linux/mkfs_ext2.c:715:1: internal compiler error: in
>>> > > > > reload_cse_simplify_operands, at postreload.c:411
>>> > > > > Please submit a full bug report,
>>> > > > > with preprocessed source if appropriate.
>>> > > > > See <http://bugs.buildroot.net/> for instructions.
>>> > > > > scripts/Makefile.build:197: recipe for target
>>> 'util-linux/mkfs_ext2.o'
>>> > > > > failed
>>> > > > > make[2]: *** [util-linux/mkfs_ext2.o] Error 1
>>> > > > > Makefile:742: recipe for target 'util-linux' failed
>>> > > > > make[1]: *** [util-linux] Error 2
>>> > > > > make[1]: Leaving directory '/home/administrator/
>>> > > > Downloads/buildroot_2017/
>>> > > > > buildroot-2017.02.5/output/build/busybox-1.26.2'
>>> > > > > package/pkg-generic.mk:216: recipe for target
>>> '/home/administrator/
>>> > > > > Downloads/buildroot_2017/buildroot-2017.02.5/output/
>>> > > > > build/busybox-1.26.2/.stamp_built' failed
>>> > > > > make: *** [/home/administrator/Downloads/buildroot_2017/
>>> > > > > buildroot-2017.02.5/output/build/busybox-1.26.2/.stamp_built]
>>> Error 2
>>> > > > >
>>> > > > > It would be really helpful is you can provide some insight and
>>> > possibly a
>>> > > > > fix/workaround.
>>> > > >
>>> > > > Have you done a clean rebuild, i.e., 'make clean; make'? See
>>> > > > http://nightly.buildroot.org/manual.html#full-rebuild .
>>> > > >
>>> > > > baruch
>>> > > >
>>> > > > > On Thu, Aug 10, 2017 at 8:55 AM, Aseem Sharma <
>>> > aseem.sharma19 at gmail.com>
>>> > > > > wrote:
>>> > > > >
>>> > > > > > Thanks Baruch & Arnout. Will give a try.
>>> > > > > >
>>> > > > > > Best Regards,
>>> > > > > > Aseem
>>> > > > > >
>>> > > > > > On Wed, Aug 9, 2017 at 10:47 PM, Baruch Siach <
>>> baruch at tkos.co.il>
>>> > > > wrote:
>>> > > > > >
>>> > > > > >> Hi Aseem,
>>> > > > > >>
>>> > > > > >> On Wed, Aug 09, 2017 at 10:03:24PM +0530, Aseem Sharma wrote:
>>> > > > > >> > Hello Baruch & Arnout,
>>> > > > > >> >
>>> > > > > >> > Thanks for your responses.
>>> > > > > >> > The board that I have is quite old with limited RAM and
>>> Flash.
>>> > > > > >> >
>>> > > > > >> > Baruch,
>>> > > > > >> > Could you please provide more details as to how do I select
>>> > "iwmmxt"
>>> > > > > >> using
>>> > > > > >> > menuconfig. As far as I remember, I do not seem to have that
>>> > option
>>> > > > in
>>> > > > > >> my
>>> > > > > >> > current buildroot release.
>>> > > > > >>
>>> > > > > >> Go to 'Target options' -> 'Target Architecture Variant', and
>>> select
>>> > > > > >> 'iwmmxt'
>>> > > > > >> (last option).
>>> > > > > >>
>>> > > > > >> > Also, as per Arnout's response to my query, I should be
>>> using ARM
>>> > > > little
>>> > > > > >> > endian with arm926tARM.
>>> > > > > >>
>>> > > > > >> As far as I know arm926t code is compatible with iwmmxt, but
>>> not
>>> > the
>>> > > > > >> other way
>>> > > > > >> around. Look for Sheeva PJ1 at [1]. See also [2].
>>> > > > > >>
>>> > > > > >> [1] https://en.wikipedia.org/wiki/
>>> List_of_ARM_microarchitectures
>>> > > > > >>
>>> > > > > >> [2] https://en.wikipedia.org/wiki/
>>> MMX_(instruction_set)#MMX_in_e
>>> > > > > >> mbedded_applications
>>> > > > > >>
>>> > > > > >> > Are these two options one and the same?
>>> > > > > >>
>>> > > > > >> I don't think so.
>>> > > > > >>
>>> > > > > >> baruch
>>> > > > > >>
>>> > > > > >> > Thanks in advance.
>>> > > > > >> >
>>> > > > > >> > Best Regards,
>>> > > > > >> > Aseem
>>> > > > > >> >
>>> > > > > >> > Sent via really tiny keyboard. Expect random auto corrects,
>>> fat
>>> > > > finger
>>> > > > > >> > typos and weirdness!!
>>> > > > > >> >
>>> > > > > >> >
>>> > > > > >> > On 09-Aug-2017 21:19, "Baruch Siach" <baruch@tkos.co.il>
>>> wrote:
>>> > > > > >> >
>>> > > > > >> > Hi Aweem,
>>> > > > > >> >
>>> > > > > >> > On Wed, Aug 09, 2017 at 06:00:55PM +0530, Aseem Sharma
>>> wrote:
>>> > > > > >> > > I am naive to buildroot & processor world trying to
>>> compile
>>> > > > > >> > > "buildroot-2017.02.5" for "Marvell ARM Armada 166E
>>> processor
>>> > > > > >> (compatible
>>> > > > > >> > to
>>> > > > > >> > > ARMv5TE instruction-set)" based old system. However, I do
>>> not
>>> > > > > >> understand
>>> > > > > >> > > the options to be selected in "make menuconfig" for
>>> > > > > >> > > 1. Target options->Target Architecture {think should be
>>> ARM -
>>> > > > little
>>> > > > > >> > endian}
>>> > > > > >> > > 2. Target options->Target Architecture variant
>>> > > > > >> > >
>>> > > > > >> > > Thanks in advance for your help.
>>> > > > > >> >
>>> > > > > >> > Based on the Armada 16x Datasheet[1], the mainline kernel
>>> > > > > >> > arch/arm/mach-mmp/Kconfig (CONFIG_CPU_PXA168) and
>>> > arch/arm/Kconfig
>>> > > > > >> > (CONFIG_IWMMXT), it seems like you need the iwmmxt ARM
>>> variant
>>> > for
>>> > > > your
>>> > > > > >> > Armada
>>> > > > > >> > 166E processor.
>>> > > > > >> >
>>> > > > > >> > [1] http://www.marvell.com.cn/appl
>>> ication-processors/armada-100/
>>> > > > > >> > assets/armada_16x_datasheet.pdf
>>> >
>>> > --
>>> >      http://baruch.siach.name/blog/                  ~. .~   Tk Open
>>> Systems
>>> > =}------------------------------------------------ooO--U--Oo
>>> o------------{=
>>> >    - baruch at tkos.co.il - tel: +972.52.368.4656, http://www.tkos.co.il
>>> -
>>>
>>> --
>>>      http://baruch.siach.name/blog/                  ~. .~   Tk Open
>>> Systems
>>> =}------------------------------------------------ooO--U--Oo
>>> o------------{=
>>>    - baruch at tkos.co.il - tel: +972.52.368.4656, http://www.tkos.co.il -
>>>
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20170810/8d74119c/attachment.html>

[Buildroot] Compiling buildroot for Arm "Armada 166E" Target

[Baruch Siach]

Hi Aseem,

On Thu, Aug 10, 2017 at 02:16:59PM +0530, Aseem Sharma wrote:
> The build passes with minimal defconfig on Latest stable release v2017.05.2
> and also on latest long term support release v2017.02.5.
> So the issue seems to be with my config settings. Is there any workarounds
> to fix/avoid the issue?

What is your config? Generate a minimal config in the file 'defconfig' with

  make savedefconfig

baruch

> On Thu, Aug 10, 2017 at 1:44 PM, Aseem Sharma <aseem.sharma19@gmail.com>
> wrote:
> > Another information that I may have missed is that I am currently using
> > Ubuntu 16.4 system, i686 arch to build source for "iwmmxt"
> >
> > -Aseem
> >
> > On Thu, Aug 10, 2017 at 1:39 PM, Aseem Sharma <aseem.sharma19@gmail.com>
> > wrote:
> >
> >> Where will i find minimal defconfig?
> >> Please note that the issue was orignally observed on latest long term
> >> support release v2017.02.5.
> >> However I would try the steps provided in your last email over Latest
> >> stable release v2017.05.2.
> >> Sorry about too many naive questions.
> >>
> >> -Aseem
> >>
> >> On Thu, Aug 10, 2017 at 12:58 PM, Baruch Siach <baruch@tkos.co.il> wrote:
> >>
> >>> Hi Aseem,
> >>>
> >>> On Thu, Aug 10, 2017 at 12:51:53PM +0530, Aseem Sharma wrote:
> >>> > Sure. Can you please give me the exact steps to be carried out.
> >>> > Also, I tried selecting other gcc versions from menuconfig but the
> >>> > compilation seems to fail all the time with one issue or the other.
> >>>
> >>> Remove your current .config, copy the minimal defconfig below into
> >>> .config,
> >>> and then do
> >>>
> >>>   make olddefconfig
> >>>   make clean
> >>>   make
> >>>
> >>> This will automatically select the gcc version which as of current
> >>> master is
> >>> 6.4.0.
> >>>
> >>> baruch
> >>>
> >>> > On 10-Aug-2017 12:43 PM, "Baruch Siach" <baruch@tkos.co.il> wrote:
> >>> >
> >>> > On Thu, Aug 10, 2017 at 12:19:33PM +0530, Aseem Sharma wrote:
> >>> > > Yes Baruch. I tried a couple of times with "make clean" & even "make
> >>> > > distclean". However, the error is consistent.
> >>> > > Found a similar issue here: https://gcc.gnu.org/bugzilla/
> >>> > > show_bug.cgi?id=40836
> >>> >
> >>> > This issue seems to be fixed since gcc 4.8.
> >>> >
> >>> > I could not reproduce this ICE on current master with the following
> >>> minimal
> >>> > defconfig:
> >>> >
> >>> > BR2_arm=y
> >>> > BR2_iwmmxt=y
> >>> >
> >>> > Can you give it a try?
> >>> >
> >>> > baruch
> >>> >
> >>> > > On Thu, Aug 10, 2017 at 12:06 PM, Baruch Siach <baruch@tkos.co.il>
> >>> wrote:
> >>> > > > On Thu, Aug 10, 2017 at 11:56:56AM +0530, Aseem Sharma wrote:
> >>> > > > > *A follow-up question:*
> >>> > > > > I selected 'iwmmxt' as per Baruch's suggestion and tried to run
> >>> > "make".
> >>> > > > > The build seems to be failing with following error message in
> >>> > > > > "busybox-1.26.2" compilation:
> >>> > > > >
> >>> > > > > util-linux/mkfs_ext2.c: In function ?mkfs_ext2_main?:
> >>> > > > > util-linux/mkfs_ext2.c:715:1: error: insn does not satisfy its
> >>> > > > constraints:
> >>> > > > >  }
> >>> > > > >  ^
> >>> > > > > (insn 1169 286 287 31 (set (reg:SI 0 r0)
> >>> > > > >         (reg:SI 80 wr0)) util-linux/mkfs_ext2.c:344 426
> >>> > > > {*iwmmxt_movsi_insn}
> >>> > > > >      (nil))
> >>> > > > > util-linux/mkfs_ext2.c:715:1: internal compiler error: in
> >>> > > > > reload_cse_simplify_operands, at postreload.c:411
> >>> > > > > Please submit a full bug report,
> >>> > > > > with preprocessed source if appropriate.
> >>> > > > > See <http://bugs.buildroot.net/> for instructions.
> >>> > > > > scripts/Makefile.build:197: recipe for target
> >>> 'util-linux/mkfs_ext2.o'
> >>> > > > > failed
> >>> > > > > make[2]: *** [util-linux/mkfs_ext2.o] Error 1
> >>> > > > > Makefile:742: recipe for target 'util-linux' failed
> >>> > > > > make[1]: *** [util-linux] Error 2
> >>> > > > > make[1]: Leaving directory '/home/administrator/
> >>> > > > Downloads/buildroot_2017/
> >>> > > > > buildroot-2017.02.5/output/build/busybox-1.26.2'
> >>> > > > > package/pkg-generic.mk:216: recipe for target
> >>> '/home/administrator/
> >>> > > > > Downloads/buildroot_2017/buildroot-2017.02.5/output/
> >>> > > > > build/busybox-1.26.2/.stamp_built' failed
> >>> > > > > make: *** [/home/administrator/Downloads/buildroot_2017/
> >>> > > > > buildroot-2017.02.5/output/build/busybox-1.26.2/.stamp_built]
> >>> Error 2
> >>> > > > >
> >>> > > > > It would be really helpful is you can provide some insight and
> >>> > possibly a
> >>> > > > > fix/workaround.

-- 
     http://baruch.siach.name/blog/                  ~. .~   Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
   - baruch at tkos.co.il - tel: +972.52.368.4656, http://www.tkos.co.il -

[Buildroot] Compiling buildroot for Arm "Armada 166E" Target

[Aseem Sharma]

Hi Baruch,

My config uses gcc v4.7. Will try and build with gcc v6.X and see if it
still fails.
Do you think generating a minimal config in defconfig file help in my
situation?

-Aseem


On Thu, Aug 10, 2017 at 2:20 PM, Baruch Siach <baruch@tkos.co.il> wrote:

> Hi Aseem,
>
> On Thu, Aug 10, 2017 at 02:16:59PM +0530, Aseem Sharma wrote:
> > The build passes with minimal defconfig on Latest stable release
> v2017.05.2
> > and also on latest long term support release v2017.02.5.
> > So the issue seems to be with my config settings. Is there any
> workarounds
> > to fix/avoid the issue?
>
> What is your config? Generate a minimal config in the file 'defconfig' with
>
>   make savedefconfig
>
> baruch
>
> > On Thu, Aug 10, 2017 at 1:44 PM, Aseem Sharma <aseem.sharma19@gmail.com>
> > wrote:
> > > Another information that I may have missed is that I am currently using
> > > Ubuntu 16.4 system, i686 arch to build source for "iwmmxt"
> > >
> > > -Aseem
> > >
> > > On Thu, Aug 10, 2017 at 1:39 PM, Aseem Sharma <
> aseem.sharma19 at gmail.com>
> > > wrote:
> > >
> > >> Where will i find minimal defconfig?
> > >> Please note that the issue was orignally observed on latest long term
> > >> support release v2017.02.5.
> > >> However I would try the steps provided in your last email over Latest
> > >> stable release v2017.05.2.
> > >> Sorry about too many naive questions.
> > >>
> > >> -Aseem
> > >>
> > >> On Thu, Aug 10, 2017 at 12:58 PM, Baruch Siach <baruch@tkos.co.il>
> wrote:
> > >>
> > >>> Hi Aseem,
> > >>>
> > >>> On Thu, Aug 10, 2017 at 12:51:53PM +0530, Aseem Sharma wrote:
> > >>> > Sure. Can you please give me the exact steps to be carried out.
> > >>> > Also, I tried selecting other gcc versions from menuconfig but the
> > >>> > compilation seems to fail all the time with one issue or the other.
> > >>>
> > >>> Remove your current .config, copy the minimal defconfig below into
> > >>> .config,
> > >>> and then do
> > >>>
> > >>>   make olddefconfig
> > >>>   make clean
> > >>>   make
> > >>>
> > >>> This will automatically select the gcc version which as of current
> > >>> master is
> > >>> 6.4.0.
> > >>>
> > >>> baruch
> > >>>
> > >>> > On 10-Aug-2017 12:43 PM, "Baruch Siach" <baruch@tkos.co.il> wrote:
> > >>> >
> > >>> > On Thu, Aug 10, 2017 at 12:19:33PM +0530, Aseem Sharma wrote:
> > >>> > > Yes Baruch. I tried a couple of times with "make clean" & even
> "make
> > >>> > > distclean". However, the error is consistent.
> > >>> > > Found a similar issue here: https://gcc.gnu.org/bugzilla/
> > >>> > > show_bug.cgi?id=40836
> > >>> >
> > >>> > This issue seems to be fixed since gcc 4.8.
> > >>> >
> > >>> > I could not reproduce this ICE on current master with the following
> > >>> minimal
> > >>> > defconfig:
> > >>> >
> > >>> > BR2_arm=y
> > >>> > BR2_iwmmxt=y
> > >>> >
> > >>> > Can you give it a try?
> > >>> >
> > >>> > baruch
> > >>> >
> > >>> > > On Thu, Aug 10, 2017 at 12:06 PM, Baruch Siach <
> baruch at tkos.co.il>
> > >>> wrote:
> > >>> > > > On Thu, Aug 10, 2017 at 11:56:56AM +0530, Aseem Sharma wrote:
> > >>> > > > > *A follow-up question:*
> > >>> > > > > I selected 'iwmmxt' as per Baruch's suggestion and tried to
> run
> > >>> > "make".
> > >>> > > > > The build seems to be failing with following error message in
> > >>> > > > > "busybox-1.26.2" compilation:
> > >>> > > > >
> > >>> > > > > util-linux/mkfs_ext2.c: In function ?mkfs_ext2_main?:
> > >>> > > > > util-linux/mkfs_ext2.c:715:1: error: insn does not satisfy
> its
> > >>> > > > constraints:
> > >>> > > > >  }
> > >>> > > > >  ^
> > >>> > > > > (insn 1169 286 287 31 (set (reg:SI 0 r0)
> > >>> > > > >         (reg:SI 80 wr0)) util-linux/mkfs_ext2.c:344 426
> > >>> > > > {*iwmmxt_movsi_insn}
> > >>> > > > >      (nil))
> > >>> > > > > util-linux/mkfs_ext2.c:715:1: internal compiler error: in
> > >>> > > > > reload_cse_simplify_operands, at postreload.c:411
> > >>> > > > > Please submit a full bug report,
> > >>> > > > > with preprocessed source if appropriate.
> > >>> > > > > See <http://bugs.buildroot.net/> for instructions.
> > >>> > > > > scripts/Makefile.build:197: recipe for target
> > >>> 'util-linux/mkfs_ext2.o'
> > >>> > > > > failed
> > >>> > > > > make[2]: *** [util-linux/mkfs_ext2.o] Error 1
> > >>> > > > > Makefile:742: recipe for target 'util-linux' failed
> > >>> > > > > make[1]: *** [util-linux] Error 2
> > >>> > > > > make[1]: Leaving directory '/home/administrator/
> > >>> > > > Downloads/buildroot_2017/
> > >>> > > > > buildroot-2017.02.5/output/build/busybox-1.26.2'
> > >>> > > > > package/pkg-generic.mk:216: recipe for target
> > >>> '/home/administrator/
> > >>> > > > > Downloads/buildroot_2017/buildroot-2017.02.5/output/
> > >>> > > > > build/busybox-1.26.2/.stamp_built' failed
> > >>> > > > > make: *** [/home/administrator/Downloads/buildroot_2017/
> > >>> > > > > buildroot-2017.02.5/output/build/busybox-1.26.2/.stamp_
> built]
> > >>> Error 2
> > >>> > > > >
> > >>> > > > > It would be really helpful is you can provide some insight
> and
> > >>> > possibly a
> > >>> > > > > fix/workaround.
>
> --
>      http://baruch.siach.name/blog/                  ~. .~   Tk Open
> Systems
> =}------------------------------------------------ooO--U--
> Ooo------------{=
>    - baruch at tkos.co.il - tel: +972.52.368.4656, http://www.tkos.co.il -
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20170810/dad904f5/attachment.html>

[Buildroot] Compiling buildroot for Arm "Armada 166E" Target

[Baruch Siach]

Hi Aseem,

On Thu, Aug 10, 2017 at 02:39:06PM +0530, Aseem Sharma wrote:
> My config uses gcc v4.7. Will try and build with gcc v6.X and see if it
> still fails.

gcc v4.7 is most likely affected by bug #40836 as you noticed. The comments in 
that bug indicate that any version later than 4.7 should work.

> Do you think generating a minimal config in defconfig file help in my
> situation?

No. It just make it easier to send to the mailing list as it discards the 
default values that make up 98% of the .config content.

baruch

> On Thu, Aug 10, 2017 at 2:20 PM, Baruch Siach <baruch@tkos.co.il> wrote:
> >
> > On Thu, Aug 10, 2017 at 02:16:59PM +0530, Aseem Sharma wrote:
> > > The build passes with minimal defconfig on Latest stable release
> > v2017.05.2
> > > and also on latest long term support release v2017.02.5.
> > > So the issue seems to be with my config settings. Is there any
> > workarounds
> > > to fix/avoid the issue?
> >
> > What is your config? Generate a minimal config in the file 'defconfig' with
> >
> >   make savedefconfig
> >
> > baruch
> >
> > > On Thu, Aug 10, 2017 at 1:44 PM, Aseem Sharma <aseem.sharma19@gmail.com>
> > > wrote:
> > > > Another information that I may have missed is that I am currently using
> > > > Ubuntu 16.4 system, i686 arch to build source for "iwmmxt"
> > > >
> > > > -Aseem
> > > >
> > > > On Thu, Aug 10, 2017 at 1:39 PM, Aseem Sharma <
> > aseem.sharma19 at gmail.com>
> > > > wrote:
> > > >
> > > >> Where will i find minimal defconfig?
> > > >> Please note that the issue was orignally observed on latest long term
> > > >> support release v2017.02.5.
> > > >> However I would try the steps provided in your last email over Latest
> > > >> stable release v2017.05.2.
> > > >> Sorry about too many naive questions.
> > > >>
> > > >> -Aseem
> > > >>
> > > >> On Thu, Aug 10, 2017 at 12:58 PM, Baruch Siach <baruch@tkos.co.il>
> > wrote:
> > > >>
> > > >>> Hi Aseem,
> > > >>>
> > > >>> On Thu, Aug 10, 2017 at 12:51:53PM +0530, Aseem Sharma wrote:
> > > >>> > Sure. Can you please give me the exact steps to be carried out.
> > > >>> > Also, I tried selecting other gcc versions from menuconfig but the
> > > >>> > compilation seems to fail all the time with one issue or the other.
> > > >>>
> > > >>> Remove your current .config, copy the minimal defconfig below into
> > > >>> .config,
> > > >>> and then do
> > > >>>
> > > >>>   make olddefconfig
> > > >>>   make clean
> > > >>>   make
> > > >>>
> > > >>> This will automatically select the gcc version which as of current
> > > >>> master is
> > > >>> 6.4.0.
> > > >>>
> > > >>> baruch
> > > >>>
> > > >>> > On 10-Aug-2017 12:43 PM, "Baruch Siach" <baruch@tkos.co.il> wrote:
> > > >>> >
> > > >>> > On Thu, Aug 10, 2017 at 12:19:33PM +0530, Aseem Sharma wrote:
> > > >>> > > Yes Baruch. I tried a couple of times with "make clean" & even
> > "make
> > > >>> > > distclean". However, the error is consistent.
> > > >>> > > Found a similar issue here: https://gcc.gnu.org/bugzilla/
> > > >>> > > show_bug.cgi?id=40836
> > > >>> >
> > > >>> > This issue seems to be fixed since gcc 4.8.
> > > >>> >
> > > >>> > I could not reproduce this ICE on current master with the following
> > > >>> minimal
> > > >>> > defconfig:
> > > >>> >
> > > >>> > BR2_arm=y
> > > >>> > BR2_iwmmxt=y
> > > >>> >
> > > >>> > Can you give it a try?
> > > >>> >
> > > >>> > baruch
> > > >>> >
> > > >>> > > On Thu, Aug 10, 2017 at 12:06 PM, Baruch Siach <
> > baruch at tkos.co.il>
> > > >>> wrote:
> > > >>> > > > On Thu, Aug 10, 2017 at 11:56:56AM +0530, Aseem Sharma wrote:
> > > >>> > > > > *A follow-up question:*
> > > >>> > > > > I selected 'iwmmxt' as per Baruch's suggestion and tried to
> > run
> > > >>> > "make".
> > > >>> > > > > The build seems to be failing with following error message in
> > > >>> > > > > "busybox-1.26.2" compilation:
> > > >>> > > > >
> > > >>> > > > > util-linux/mkfs_ext2.c: In function ?mkfs_ext2_main?:
> > > >>> > > > > util-linux/mkfs_ext2.c:715:1: error: insn does not satisfy
> > its
> > > >>> > > > constraints:
> > > >>> > > > >  }
> > > >>> > > > >  ^
> > > >>> > > > > (insn 1169 286 287 31 (set (reg:SI 0 r0)
> > > >>> > > > >         (reg:SI 80 wr0)) util-linux/mkfs_ext2.c:344 426
> > > >>> > > > {*iwmmxt_movsi_insn}
> > > >>> > > > >      (nil))
> > > >>> > > > > util-linux/mkfs_ext2.c:715:1: internal compiler error: in
> > > >>> > > > > reload_cse_simplify_operands, at postreload.c:411
> > > >>> > > > > Please submit a full bug report,
> > > >>> > > > > with preprocessed source if appropriate.
> > > >>> > > > > See <http://bugs.buildroot.net/> for instructions.
> > > >>> > > > > scripts/Makefile.build:197: recipe for target
> > > >>> 'util-linux/mkfs_ext2.o'
> > > >>> > > > > failed
> > > >>> > > > > make[2]: *** [util-linux/mkfs_ext2.o] Error 1
> > > >>> > > > > Makefile:742: recipe for target 'util-linux' failed
> > > >>> > > > > make[1]: *** [util-linux] Error 2
> > > >>> > > > > make[1]: Leaving directory '/home/administrator/
> > > >>> > > > Downloads/buildroot_2017/
> > > >>> > > > > buildroot-2017.02.5/output/build/busybox-1.26.2'
> > > >>> > > > > package/pkg-generic.mk:216: recipe for target
> > > >>> '/home/administrator/
> > > >>> > > > > Downloads/buildroot_2017/buildroot-2017.02.5/output/
> > > >>> > > > > build/busybox-1.26.2/.stamp_built' failed
> > > >>> > > > > make: *** [/home/administrator/Downloads/buildroot_2017/
> > > >>> > > > > buildroot-2017.02.5/output/build/busybox-1.26.2/.stamp_
> > built]
> > > >>> Error 2
> > > >>> > > > >
> > > >>> > > > > It would be really helpful is you can provide some insight
> > and
> > > >>> > possibly a
> > > >>> > > > > fix/workaround.
> >
> > --
> >      http://baruch.siach.name/blog/                  ~. .~   Tk Open
> > Systems
> > =}------------------------------------------------ooO--U--
> > Ooo------------{=
> >    - baruch at tkos.co.il - tel: +972.52.368.4656, http://www.tkos.co.il -
> >

-- 
     http://baruch.siach.name/blog/                  ~. .~   Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
   - baruch at tkos.co.il - tel: +972.52.368.4656, http://www.tkos.co.il -

[Buildroot] Compiling buildroot for Arm "Armada 166E" Target

[Aseem Sharma]

Hi Baruch,

It still seems to be an issue with Gcc=v6.X :-(
In fact I have tried using all the available Gcc version from menuconfig
and its still fails. Following is the exact error message for your
reference:

In file included from lib/xmlparse.c:36:0:
lib/siphash.h: In function ?sip24_final?:
lib/siphash.h:247:1: error: unrecognizable insn:
 } /* sip24_final() */
 ^
(insn 78 77 79 11 (set (reg:DI 188)
        (xor:DI (reg:DI 189)
            (const_int 255 [0xff]))) lib/siphash.h:243 -1
     (nil))
lib/siphash.h:247:1: internal compiler error: in extract_insn, at
recog.c:2287
Please submit a full bug report,
with preprocessed source if appropriate.
See <http://bugs.buildroot.net/> for instructions.
Makefile:213: recipe for target 'lib/xmlparse.lo' failed
make[1]: *** [lib/xmlparse.lo] Error 1
make[1]: *** Waiting for unfinished jobs....
make[1]: Leaving directory '/home/administrator/Downloads/buildroot_2017/
buildroot-2017.02.5/output/build/expat-2.2.2'
package/pkg-generic.mk:216: recipe for target '/home/administrator/
Downloads/buildroot_2017/buildroot-2017.02.5/output/
build/expat-2.2.2/.stamp_built' failed
make: *** [/home/administrator/Downloads/buildroot_2017/
buildroot-2017.02.5/output/build/expat-2.2.2/.stamp_built] Error 2


Here is my config for your reference:

BR2_arm=y
BR2_iwmmxt=y
BR2_CCACHE=y
BR2_KERNEL_HEADERS_4_9=y
BR2_TOOLCHAIN_BUILDROOT_LOCALE=y
BR2_TOOLCHAIN_BUILDROOT_USE_SSP=y
BR2_GCC_VERSION_6_X=y
BR2_TOOLCHAIN_BUILDROOT_CXX=y
BR2_GCC_ENABLE_LTO=y
BR2_TARGET_GENERIC_ROOT_PASSWD="ASEEM"
BR2_LINUX_KERNEL=y
BR2_LINUX_KERNEL_USE_ARCH_DEFAULT_CONFIG=y
BR2_PACKAGE_QT5=y
BR2_PACKAGE_QT5_VERSION_5_6=y
BR2_PACKAGE_QT5BASE_CONCURRENT=y
BR2_PACKAGE_QT5BASE_SQLITE_QT=y
BR2_PACKAGE_QT5BASE_FONTCONFIG=y
BR2_PACKAGE_QT5BASE_GIF=y
BR2_PACKAGE_QT5BASE_JPEG=y
BR2_PACKAGE_QT5BASE_PNG=y
BR2_PACKAGE_QT5BASE_TSLIB=y
BR2_PACKAGE_QT5IMAGEFORMATS=y
BR2_PACKAGE_QT5LOCATION=y
BR2_PACKAGE_QT5SVG=y
BR2_PACKAGE_QT5WEBCHANNEL=y
BR2_PACKAGE_QT5XMLPATTERNS=y
BR2_PACKAGE_QT_WEBKIT_KIOSK=y
BR2_PACKAGE_POSTGRESQL=y
BR2_PACKAGE_SQLITE_STAT3=y
BR2_PACKAGE_SQLITE_ENABLE_FTS3=y
BR2_PACKAGE_SQLITE_ENABLE_UNLOCK_NOTIFY=y
BR2_PACKAGE_GIFLIB=y
BR2_PACKAGE_JPEG_TURBO=y
BR2_PACKAGE_OPENJPEG=y
BR2_PACKAGE_ANGULARJS=y
BR2_PACKAGE_ANGULAR_WEBSOCKET=y
BR2_PACKAGE_JQUERY=y
BR2_PACKAGE_JQUERY_DATETIMEPICKER=y
BR2_PACKAGE_JQUERY_SIDEBAR=y
BR2_PACKAGE_JSMIN=y
BR2_PACKAGE_JSON_JAVASCRIPT=y
BR2_PACKAGE_LIBMPEG2=y
BR2_TARGET_ROOTFS_JFFS2=y
BR2_TARGET_ROOTFS_TAR_XZ=y
BR2_TARGET_UBOOT=y
BR2_TARGET_UBOOT_BOARDNAME="ASEEM"
BR2_TARGET_UBOOT_NEEDS_OPENSSL=y

APPRECIATE YOUR HELP AND TIME ON THIS.
THANK YOU!

Best Regards,
Aseem

On Thu, Aug 10, 2017 at 2:52 PM, Baruch Siach <baruch@tkos.co.il> wrote:

> Hi Aseem,
>
> On Thu, Aug 10, 2017 at 02:39:06PM +0530, Aseem Sharma wrote:
> > My config uses gcc v4.7. Will try and build with gcc v6.X and see if it
> > still fails.
>
> gcc v4.7 is most likely affected by bug #40836 as you noticed. The
> comments in
> that bug indicate that any version later than 4.7 should work.
>
> > Do you think generating a minimal config in defconfig file help in my
> > situation?
>
> No. It just make it easier to send to the mailing list as it discards the
> default values that make up 98% of the .config content.
>
> baruch
>
> > On Thu, Aug 10, 2017 at 2:20 PM, Baruch Siach <baruch@tkos.co.il> wrote:
> > >
> > > On Thu, Aug 10, 2017 at 02:16:59PM +0530, Aseem Sharma wrote:
> > > > The build passes with minimal defconfig on Latest stable release
> > > v2017.05.2
> > > > and also on latest long term support release v2017.02.5.
> > > > So the issue seems to be with my config settings. Is there any
> > > workarounds
> > > > to fix/avoid the issue?
> > >
> > > What is your config? Generate a minimal config in the file 'defconfig'
> with
> > >
> > >   make savedefconfig
> > >
> > > baruch
> > >
> > > > On Thu, Aug 10, 2017 at 1:44 PM, Aseem Sharma <
> aseem.sharma19 at gmail.com>
> > > > wrote:
> > > > > Another information that I may have missed is that I am currently
> using
> > > > > Ubuntu 16.4 system, i686 arch to build source for "iwmmxt"
> > > > >
> > > > > -Aseem
> > > > >
> > > > > On Thu, Aug 10, 2017 at 1:39 PM, Aseem Sharma <
> > > aseem.sharma19 at gmail.com>
> > > > > wrote:
> > > > >
> > > > >> Where will i find minimal defconfig?
> > > > >> Please note that the issue was orignally observed on latest long
> term
> > > > >> support release v2017.02.5.
> > > > >> However I would try the steps provided in your last email over
> Latest
> > > > >> stable release v2017.05.2.
> > > > >> Sorry about too many naive questions.
> > > > >>
> > > > >> -Aseem
> > > > >>
> > > > >> On Thu, Aug 10, 2017 at 12:58 PM, Baruch Siach <baruch@tkos.co.il
> >
> > > wrote:
> > > > >>
> > > > >>> Hi Aseem,
> > > > >>>
> > > > >>> On Thu, Aug 10, 2017 at 12:51:53PM +0530, Aseem Sharma wrote:
> > > > >>> > Sure. Can you please give me the exact steps to be carried out.
> > > > >>> > Also, I tried selecting other gcc versions from menuconfig but
> the
> > > > >>> > compilation seems to fail all the time with one issue or the
> other.
> > > > >>>
> > > > >>> Remove your current .config, copy the minimal defconfig below
> into
> > > > >>> .config,
> > > > >>> and then do
> > > > >>>
> > > > >>>   make olddefconfig
> > > > >>>   make clean
> > > > >>>   make
> > > > >>>
> > > > >>> This will automatically select the gcc version which as of
> current
> > > > >>> master is
> > > > >>> 6.4.0.
> > > > >>>
> > > > >>> baruch
> > > > >>>
> > > > >>> > On 10-Aug-2017 12:43 PM, "Baruch Siach" <baruch@tkos.co.il>
> wrote:
> > > > >>> >
> > > > >>> > On Thu, Aug 10, 2017 at 12:19:33PM +0530, Aseem Sharma wrote:
> > > > >>> > > Yes Baruch. I tried a couple of times with "make clean" &
> even
> > > "make
> > > > >>> > > distclean". However, the error is consistent.
> > > > >>> > > Found a similar issue here: https://gcc.gnu.org/bugzilla/
> > > > >>> > > show_bug.cgi?id=40836
> > > > >>> >
> > > > >>> > This issue seems to be fixed since gcc 4.8.
> > > > >>> >
> > > > >>> > I could not reproduce this ICE on current master with the
> following
> > > > >>> minimal
> > > > >>> > defconfig:
> > > > >>> >
> > > > >>> > BR2_arm=y
> > > > >>> > BR2_iwmmxt=y
> > > > >>> >
> > > > >>> > Can you give it a try?
> > > > >>> >
> > > > >>> > baruch
> > > > >>> >
> > > > >>> > > On Thu, Aug 10, 2017 at 12:06 PM, Baruch Siach <
> > > baruch at tkos.co.il>
> > > > >>> wrote:
> > > > >>> > > > On Thu, Aug 10, 2017 at 11:56:56AM +0530, Aseem Sharma
> wrote:
> > > > >>> > > > > *A follow-up question:*
> > > > >>> > > > > I selected 'iwmmxt' as per Baruch's suggestion and tried
> to
> > > run
> > > > >>> > "make".
> > > > >>> > > > > The build seems to be failing with following error
> message in
> > > > >>> > > > > "busybox-1.26.2" compilation:
> > > > >>> > > > >
> > > > >>> > > > > util-linux/mkfs_ext2.c: In function ?mkfs_ext2_main?:
> > > > >>> > > > > util-linux/mkfs_ext2.c:715:1: error: insn does not
> satisfy
> > > its
> > > > >>> > > > constraints:
> > > > >>> > > > >  }
> > > > >>> > > > >  ^
> > > > >>> > > > > (insn 1169 286 287 31 (set (reg:SI 0 r0)
> > > > >>> > > > >         (reg:SI 80 wr0)) util-linux/mkfs_ext2.c:344 426
> > > > >>> > > > {*iwmmxt_movsi_insn}
> > > > >>> > > > >      (nil))
> > > > >>> > > > > util-linux/mkfs_ext2.c:715:1: internal compiler error: in
> > > > >>> > > > > reload_cse_simplify_operands, at postreload.c:411
> > > > >>> > > > > Please submit a full bug report,
> > > > >>> > > > > with preprocessed source if appropriate.
> > > > >>> > > > > See <http://bugs.buildroot.net/> for instructions.
> > > > >>> > > > > scripts/Makefile.build:197: recipe for target
> > > > >>> 'util-linux/mkfs_ext2.o'
> > > > >>> > > > > failed
> > > > >>> > > > > make[2]: *** [util-linux/mkfs_ext2.o] Error 1
> > > > >>> > > > > Makefile:742: recipe for target 'util-linux' failed
> > > > >>> > > > > make[1]: *** [util-linux] Error 2
> > > > >>> > > > > make[1]: Leaving directory '/home/administrator/
> > > > >>> > > > Downloads/buildroot_2017/
> > > > >>> > > > > buildroot-2017.02.5/output/build/busybox-1.26.2'
> > > > >>> > > > > package/pkg-generic.mk:216: recipe for target
> > > > >>> '/home/administrator/
> > > > >>> > > > > Downloads/buildroot_2017/buildroot-2017.02.5/output/
> > > > >>> > > > > build/busybox-1.26.2/.stamp_built' failed
> > > > >>> > > > > make: *** [/home/administrator/Downloads/buildroot_2017/
> > > > >>> > > > > buildroot-2017.02.5/output/build/busybox-1.26.2/.stamp_
> > > built]
> > > > >>> Error 2
> > > > >>> > > > >
> > > > >>> > > > > It would be really helpful is you can provide some
> insight
> > > and
> > > > >>> > possibly a
> > > > >>> > > > > fix/workaround.
> > >
> > > --
> > >      http://baruch.siach.name/blog/                  ~. .~   Tk Open
> > > Systems
> > > =}------------------------------------------------ooO--U--
> > > Ooo------------{=
> > >    - baruch at tkos.co.il - tel: +972.52.368.4656, http://www.tkos.co.il
> -
> > >
>
> --
>      http://baruch.siach.name/blog/                  ~. .~   Tk Open
> Systems
> =}------------------------------------------------ooO--U--
> Ooo------------{=
>    - baruch at tkos.co.il - tel: +972.52.368.4656, http://www.tkos.co.il -
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20170810/25172d4b/attachment-0001.html>

[Buildroot] Compiling buildroot for Arm "Armada 166E" Target

[Baruch Siach]

Hi Aseem,

On Thu, Aug 10, 2017 at 03:27:26PM +0530, Aseem Sharma wrote:
> It still seems to be an issue with Gcc=v6.X :-(
> In fact I have tried using all the available Gcc version from menuconfig
> and its still fails. Following is the exact error message for your
> reference:
> 
> In file included from lib/xmlparse.c:36:0:
> lib/siphash.h: In function ?sip24_final?:
> lib/siphash.h:247:1: error: unrecognizable insn:
>  } /* sip24_final() */
>  ^
> (insn 78 77 79 11 (set (reg:DI 188)
>         (xor:DI (reg:DI 189)
>             (const_int 255 [0xff]))) lib/siphash.h:243 -1
>      (nil))
> lib/siphash.h:247:1: internal compiler error: in extract_insn, at
> recog.c:2287
> Please submit a full bug report,
> with preprocessed source if appropriate.
> See <http://bugs.buildroot.net/> for instructions.
> Makefile:213: recipe for target 'lib/xmlparse.lo' failed
> make[1]: *** [lib/xmlparse.lo] Error 1
> make[1]: *** Waiting for unfinished jobs....
> make[1]: Leaving directory '/home/administrator/Downloads/buildroot_2017/
> buildroot-2017.02.5/output/build/expat-2.2.2'
> package/pkg-generic.mk:216: recipe for target '/home/administrator/
> Downloads/buildroot_2017/buildroot-2017.02.5/output/
> build/expat-2.2.2/.stamp_built' failed
> make: *** [/home/administrator/Downloads/buildroot_2017/
> buildroot-2017.02.5/output/build/expat-2.2.2/.stamp_built] Error 2

I reproduced the exact same issue here on current master as of c2da653d085df1. 
I only run 'make expat' to shorten build time.

I think you should to take this to the gcc bug tracker. I don't think any of 
the Buildroot gcc patches have anything to do with that, but I'll let the 
toolchain experts on the list share their opinion.

baruch

> Here is my config for your reference:
> 
> BR2_arm=y
> BR2_iwmmxt=y
> BR2_CCACHE=y
> BR2_KERNEL_HEADERS_4_9=y
> BR2_TOOLCHAIN_BUILDROOT_LOCALE=y
> BR2_TOOLCHAIN_BUILDROOT_USE_SSP=y
> BR2_GCC_VERSION_6_X=y
> BR2_TOOLCHAIN_BUILDROOT_CXX=y
> BR2_GCC_ENABLE_LTO=y
> BR2_TARGET_GENERIC_ROOT_PASSWD="ASEEM"
> BR2_LINUX_KERNEL=y
> BR2_LINUX_KERNEL_USE_ARCH_DEFAULT_CONFIG=y
> BR2_PACKAGE_QT5=y
> BR2_PACKAGE_QT5_VERSION_5_6=y
> BR2_PACKAGE_QT5BASE_CONCURRENT=y
> BR2_PACKAGE_QT5BASE_SQLITE_QT=y
> BR2_PACKAGE_QT5BASE_FONTCONFIG=y
> BR2_PACKAGE_QT5BASE_GIF=y
> BR2_PACKAGE_QT5BASE_JPEG=y
> BR2_PACKAGE_QT5BASE_PNG=y
> BR2_PACKAGE_QT5BASE_TSLIB=y
> BR2_PACKAGE_QT5IMAGEFORMATS=y
> BR2_PACKAGE_QT5LOCATION=y
> BR2_PACKAGE_QT5SVG=y
> BR2_PACKAGE_QT5WEBCHANNEL=y
> BR2_PACKAGE_QT5XMLPATTERNS=y
> BR2_PACKAGE_QT_WEBKIT_KIOSK=y
> BR2_PACKAGE_POSTGRESQL=y
> BR2_PACKAGE_SQLITE_STAT3=y
> BR2_PACKAGE_SQLITE_ENABLE_FTS3=y
> BR2_PACKAGE_SQLITE_ENABLE_UNLOCK_NOTIFY=y
> BR2_PACKAGE_GIFLIB=y
> BR2_PACKAGE_JPEG_TURBO=y
> BR2_PACKAGE_OPENJPEG=y
> BR2_PACKAGE_ANGULARJS=y
> BR2_PACKAGE_ANGULAR_WEBSOCKET=y
> BR2_PACKAGE_JQUERY=y
> BR2_PACKAGE_JQUERY_DATETIMEPICKER=y
> BR2_PACKAGE_JQUERY_SIDEBAR=y
> BR2_PACKAGE_JSMIN=y
> BR2_PACKAGE_JSON_JAVASCRIPT=y
> BR2_PACKAGE_LIBMPEG2=y
> BR2_TARGET_ROOTFS_JFFS2=y
> BR2_TARGET_ROOTFS_TAR_XZ=y
> BR2_TARGET_UBOOT=y
> BR2_TARGET_UBOOT_BOARDNAME="ASEEM"
> BR2_TARGET_UBOOT_NEEDS_OPENSSL=y
> 
> APPRECIATE YOUR HELP AND TIME ON THIS.
> THANK YOU!
> 
> Best Regards,
> Aseem
> 
> On Thu, Aug 10, 2017 at 2:52 PM, Baruch Siach <baruch@tkos.co.il> wrote:
> 
> > Hi Aseem,
> >
> > On Thu, Aug 10, 2017 at 02:39:06PM +0530, Aseem Sharma wrote:
> > > My config uses gcc v4.7. Will try and build with gcc v6.X and see if it
> > > still fails.
> >
> > gcc v4.7 is most likely affected by bug #40836 as you noticed. The
> > comments in
> > that bug indicate that any version later than 4.7 should work.
> >
> > > Do you think generating a minimal config in defconfig file help in my
> > > situation?
> >
> > No. It just make it easier to send to the mailing list as it discards the
> > default values that make up 98% of the .config content.
> >
> > baruch
> >
> > > On Thu, Aug 10, 2017 at 2:20 PM, Baruch Siach <baruch@tkos.co.il> wrote:
> > > >
> > > > On Thu, Aug 10, 2017 at 02:16:59PM +0530, Aseem Sharma wrote:
> > > > > The build passes with minimal defconfig on Latest stable release
> > > > v2017.05.2
> > > > > and also on latest long term support release v2017.02.5.
> > > > > So the issue seems to be with my config settings. Is there any
> > > > workarounds
> > > > > to fix/avoid the issue?
> > > >
> > > > What is your config? Generate a minimal config in the file 'defconfig'
> > with
> > > >
> > > >   make savedefconfig
> > > >
> > > > baruch
> > > >
> > > > > On Thu, Aug 10, 2017 at 1:44 PM, Aseem Sharma <
> > aseem.sharma19 at gmail.com>
> > > > > wrote:
> > > > > > Another information that I may have missed is that I am currently
> > using
> > > > > > Ubuntu 16.4 system, i686 arch to build source for "iwmmxt"
> > > > > >
> > > > > > -Aseem
> > > > > >
> > > > > > On Thu, Aug 10, 2017 at 1:39 PM, Aseem Sharma <
> > > > aseem.sharma19 at gmail.com>
> > > > > > wrote:
> > > > > >
> > > > > >> Where will i find minimal defconfig?
> > > > > >> Please note that the issue was orignally observed on latest long
> > term
> > > > > >> support release v2017.02.5.
> > > > > >> However I would try the steps provided in your last email over
> > Latest
> > > > > >> stable release v2017.05.2.
> > > > > >> Sorry about too many naive questions.
> > > > > >>
> > > > > >> -Aseem
> > > > > >>
> > > > > >> On Thu, Aug 10, 2017 at 12:58 PM, Baruch Siach <baruch@tkos.co.il
> > >
> > > > wrote:
> > > > > >>
> > > > > >>> Hi Aseem,
> > > > > >>>
> > > > > >>> On Thu, Aug 10, 2017 at 12:51:53PM +0530, Aseem Sharma wrote:
> > > > > >>> > Sure. Can you please give me the exact steps to be carried out.
> > > > > >>> > Also, I tried selecting other gcc versions from menuconfig but
> > the
> > > > > >>> > compilation seems to fail all the time with one issue or the
> > other.
> > > > > >>>
> > > > > >>> Remove your current .config, copy the minimal defconfig below
> > into
> > > > > >>> .config,
> > > > > >>> and then do
> > > > > >>>
> > > > > >>>   make olddefconfig
> > > > > >>>   make clean
> > > > > >>>   make
> > > > > >>>
> > > > > >>> This will automatically select the gcc version which as of
> > current
> > > > > >>> master is
> > > > > >>> 6.4.0.
> > > > > >>>
> > > > > >>> baruch
> > > > > >>>
> > > > > >>> > On 10-Aug-2017 12:43 PM, "Baruch Siach" <baruch@tkos.co.il>
> > wrote:
> > > > > >>> >
> > > > > >>> > On Thu, Aug 10, 2017 at 12:19:33PM +0530, Aseem Sharma wrote:
> > > > > >>> > > Yes Baruch. I tried a couple of times with "make clean" &
> > even
> > > > "make
> > > > > >>> > > distclean". However, the error is consistent.
> > > > > >>> > > Found a similar issue here: https://gcc.gnu.org/bugzilla/
> > > > > >>> > > show_bug.cgi?id=40836
> > > > > >>> >
> > > > > >>> > This issue seems to be fixed since gcc 4.8.
> > > > > >>> >
> > > > > >>> > I could not reproduce this ICE on current master with the
> > following
> > > > > >>> minimal
> > > > > >>> > defconfig:
> > > > > >>> >
> > > > > >>> > BR2_arm=y
> > > > > >>> > BR2_iwmmxt=y
> > > > > >>> >
> > > > > >>> > Can you give it a try?
> > > > > >>> >
> > > > > >>> > baruch
> > > > > >>> >
> > > > > >>> > > On Thu, Aug 10, 2017 at 12:06 PM, Baruch Siach <
> > > > baruch at tkos.co.il>
> > > > > >>> wrote:
> > > > > >>> > > > On Thu, Aug 10, 2017 at 11:56:56AM +0530, Aseem Sharma
> > wrote:
> > > > > >>> > > > > *A follow-up question:*
> > > > > >>> > > > > I selected 'iwmmxt' as per Baruch's suggestion and tried
> > to
> > > > run
> > > > > >>> > "make".
> > > > > >>> > > > > The build seems to be failing with following error
> > message in
> > > > > >>> > > > > "busybox-1.26.2" compilation:
> > > > > >>> > > > >
> > > > > >>> > > > > util-linux/mkfs_ext2.c: In function ?mkfs_ext2_main?:
> > > > > >>> > > > > util-linux/mkfs_ext2.c:715:1: error: insn does not
> > satisfy
> > > > its
> > > > > >>> > > > constraints:
> > > > > >>> > > > >  }
> > > > > >>> > > > >  ^
> > > > > >>> > > > > (insn 1169 286 287 31 (set (reg:SI 0 r0)
> > > > > >>> > > > >         (reg:SI 80 wr0)) util-linux/mkfs_ext2.c:344 426
> > > > > >>> > > > {*iwmmxt_movsi_insn}
> > > > > >>> > > > >      (nil))
> > > > > >>> > > > > util-linux/mkfs_ext2.c:715:1: internal compiler error: in
> > > > > >>> > > > > reload_cse_simplify_operands, at postreload.c:411
> > > > > >>> > > > > Please submit a full bug report,
> > > > > >>> > > > > with preprocessed source if appropriate.
> > > > > >>> > > > > See <http://bugs.buildroot.net/> for instructions.
> > > > > >>> > > > > scripts/Makefile.build:197: recipe for target
> > > > > >>> 'util-linux/mkfs_ext2.o'
> > > > > >>> > > > > failed
> > > > > >>> > > > > make[2]: *** [util-linux/mkfs_ext2.o] Error 1
> > > > > >>> > > > > Makefile:742: recipe for target 'util-linux' failed
> > > > > >>> > > > > make[1]: *** [util-linux] Error 2
> > > > > >>> > > > > make[1]: Leaving directory '/home/administrator/
> > > > > >>> > > > Downloads/buildroot_2017/
> > > > > >>> > > > > buildroot-2017.02.5/output/build/busybox-1.26.2'
> > > > > >>> > > > > package/pkg-generic.mk:216: recipe for target
> > > > > >>> '/home/administrator/
> > > > > >>> > > > > Downloads/buildroot_2017/buildroot-2017.02.5/output/
> > > > > >>> > > > > build/busybox-1.26.2/.stamp_built' failed
> > > > > >>> > > > > make: *** [/home/administrator/Downloads/buildroot_2017/
> > > > > >>> > > > > buildroot-2017.02.5/output/build/busybox-1.26.2/.stamp_
> > > > built]
> > > > > >>> Error 2
> > > > > >>> > > > >
> > > > > >>> > > > > It would be really helpful is you can provide some
> > insight
> > > > and
> > > > > >>> > possibly a
> > > > > >>> > > > > fix/workaround.

-- 
     http://baruch.siach.name/blog/                  ~. .~   Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
   - baruch at tkos.co.il - tel: +972.52.368.4656, http://www.tkos.co.il -

[Buildroot] Compiling buildroot for Arm "Armada 166E" Target

[Arnout Vandecappelle]

On 10-08-17 12:33, Baruch Siach wrote:
> Hi Aseem,
> 
> On Thu, Aug 10, 2017 at 03:27:26PM +0530, Aseem Sharma wrote:
>> It still seems to be an issue with Gcc=v6.X :-(
>> In fact I have tried using all the available Gcc version from menuconfig
>> and its still fails. Following is the exact error message for your
>> reference:
>>
>> In file included from lib/xmlparse.c:36:0:
>> lib/siphash.h: In function ?sip24_final?:
>> lib/siphash.h:247:1: error: unrecognizable insn:
>>  } /* sip24_final() */
>>  ^
>> (insn 78 77 79 11 (set (reg:DI 188)
>>         (xor:DI (reg:DI 189)
>>             (const_int 255 [0xff]))) lib/siphash.h:243 -1
>>      (nil))
>> lib/siphash.h:247:1: internal compiler error: in extract_insn, at
>> recog.c:2287
>> Please submit a full bug report,
>> with preprocessed source if appropriate.
>> See <http://bugs.buildroot.net/> for instructions.
>> Makefile:213: recipe for target 'lib/xmlparse.lo' failed
>> make[1]: *** [lib/xmlparse.lo] Error 1
>> make[1]: *** Waiting for unfinished jobs....
>> make[1]: Leaving directory '/home/administrator/Downloads/buildroot_2017/
>> buildroot-2017.02.5/output/build/expat-2.2.2'
>> package/pkg-generic.mk:216: recipe for target '/home/administrator/
>> Downloads/buildroot_2017/buildroot-2017.02.5/output/
>> build/expat-2.2.2/.stamp_built' failed
>> make: *** [/home/administrator/Downloads/buildroot_2017/
>> buildroot-2017.02.5/output/build/expat-2.2.2/.stamp_built] Error 2
> I reproduced the exact same issue here on current master as of c2da653d085df1. 
> I only run 'make expat' to shorten build time.
> 
> I think you should to take this to the gcc bug tracker. I don't think any of 
> the Buildroot gcc patches have anything to do with that, but I'll let the 
> toolchain experts on the list share their opinion.

 I didn't check but I indeed doubt that any of Buildroot's gcc patches could
have anything to do with it.

 To be able to report it to the gcc bug tracker, it would have to be reproduced
with current gcc master and with a minimal piece of code that exposes the bug.
Quite a bit of work...

 Aseem, to unblock you, I think it's best if you just use the much better tested
and compatible arm926t CPU choice. It will result in slightly less efficient
code because it won't make use of the iwmmx2 instructions, but I doubt that it
will have more than a few % performance impact on generic programs.

 Regards,
 Arnout

-- 
Arnout Vandecappelle                          arnout at mind be
Senior Embedded Software Architect            +32-16-286500
Essensium/Mind                                http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium           BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint:  7493 020B C7E3 8618 8DEC 222C 82EB F404 F9AC 0DDF

[Buildroot] Compiling buildroot for Arm "Armada 166E" Target

[Aseem Sharma]

Thanks Arnout & Baruch for your inputs & time.
I will try "arm926t" and see if that works for me.

Best Regards,
Aseem

On Thu, Aug 10, 2017 at 4:31 PM, Arnout Vandecappelle <arnout@mind.be>
wrote:

>
>
> On 10-08-17 12:33, Baruch Siach wrote:
> > Hi Aseem,
> >
> > On Thu, Aug 10, 2017 at 03:27:26PM +0530, Aseem Sharma wrote:
> >> It still seems to be an issue with Gcc=v6.X :-(
> >> In fact I have tried using all the available Gcc version from menuconfig
> >> and its still fails. Following is the exact error message for your
> >> reference:
> >>
> >> In file included from lib/xmlparse.c:36:0:
> >> lib/siphash.h: In function ?sip24_final?:
> >> lib/siphash.h:247:1: error: unrecognizable insn:
> >>  } /* sip24_final() */
> >>  ^
> >> (insn 78 77 79 11 (set (reg:DI 188)
> >>         (xor:DI (reg:DI 189)
> >>             (const_int 255 [0xff]))) lib/siphash.h:243 -1
> >>      (nil))
> >> lib/siphash.h:247:1: internal compiler error: in extract_insn, at
> >> recog.c:2287
> >> Please submit a full bug report,
> >> with preprocessed source if appropriate.
> >> See <http://bugs.buildroot.net/> for instructions.
> >> Makefile:213: recipe for target 'lib/xmlparse.lo' failed
> >> make[1]: *** [lib/xmlparse.lo] Error 1
> >> make[1]: *** Waiting for unfinished jobs....
> >> make[1]: Leaving directory '/home/administrator/
> Downloads/buildroot_2017/
> >> buildroot-2017.02.5/output/build/expat-2.2.2'
> >> package/pkg-generic.mk:216: recipe for target '/home/administrator/
> >> Downloads/buildroot_2017/buildroot-2017.02.5/output/
> >> build/expat-2.2.2/.stamp_built' failed
> >> make: *** [/home/administrator/Downloads/buildroot_2017/
> >> buildroot-2017.02.5/output/build/expat-2.2.2/.stamp_built] Error 2
> > I reproduced the exact same issue here on current master as of
> c2da653d085df1.
> > I only run 'make expat' to shorten build time.
> >
> > I think you should to take this to the gcc bug tracker. I don't think
> any of
> > the Buildroot gcc patches have anything to do with that, but I'll let the
> > toolchain experts on the list share their opinion.
>
>  I didn't check but I indeed doubt that any of Buildroot's gcc patches
> could
> have anything to do with it.
>
>  To be able to report it to the gcc bug tracker, it would have to be
> reproduced
> with current gcc master and with a minimal piece of code that exposes the
> bug.
> Quite a bit of work...
>
>  Aseem, to unblock you, I think it's best if you just use the much better
> tested
> and compatible arm926t CPU choice. It will result in slightly less
> efficient
> code because it won't make use of the iwmmx2 instructions, but I doubt
> that it
> will have more than a few % performance impact on generic programs.
>
>  Regards,
>  Arnout
>
> --
> Arnout Vandecappelle                          arnout at mind be
> Senior Embedded Software Architect            +32-16-286500
> Essensium/Mind                                http://www.mind.be
> G.Geenslaan 9, 3001 Leuven, Belgium           BE 872 984 063 RPR Leuven
> LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
> GPG fingerprint:  7493 020B C7E3 8618 8DEC 222C 82EB F404 F9AC 0DDF
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20170810/d0b5a073/attachment.html>

[Buildroot] Compiling buildroot for Arm "Armada 166E" Target

[Aseem Sharma]

Hi Arnout/Baruch,

I have successfully created a rootfs and zImage for my device. Thanks to
your suggestions/help in achieving this.
However, I have another not so related question:

How do I setup serial console on my device? I am not able to find the usual
"CONFIG_CMDLINE" option in menuconfig to be able to set kernel command line
parameter.
It will be really helpful if you can help me with the procedure/workaround
to be able to give command line parameter to the kernel. Or any other means
to redirect the output to ttyS0.

Thanks & Regards,
Aseem

On Thu, Aug 10, 2017 at 4:36 PM, Aseem Sharma <aseem.sharma19@gmail.com>
wrote:

> Thanks Arnout & Baruch for your inputs & time.
> I will try "arm926t" and see if that works for me.
>
> Best Regards,
> Aseem
>
> On Thu, Aug 10, 2017 at 4:31 PM, Arnout Vandecappelle <arnout@mind.be>
> wrote:
>
>>
>>
>> On 10-08-17 12:33, Baruch Siach wrote:
>> > Hi Aseem,
>> >
>> > On Thu, Aug 10, 2017 at 03:27:26PM +0530, Aseem Sharma wrote:
>> >> It still seems to be an issue with Gcc=v6.X :-(
>> >> In fact I have tried using all the available Gcc version from
>> menuconfig
>> >> and its still fails. Following is the exact error message for your
>> >> reference:
>> >>
>> >> In file included from lib/xmlparse.c:36:0:
>> >> lib/siphash.h: In function ?sip24_final?:
>> >> lib/siphash.h:247:1: error: unrecognizable insn:
>> >>  } /* sip24_final() */
>> >>  ^
>> >> (insn 78 77 79 11 (set (reg:DI 188)
>> >>         (xor:DI (reg:DI 189)
>> >>             (const_int 255 [0xff]))) lib/siphash.h:243 -1
>> >>      (nil))
>> >> lib/siphash.h:247:1: internal compiler error: in extract_insn, at
>> >> recog.c:2287
>> >> Please submit a full bug report,
>> >> with preprocessed source if appropriate.
>> >> See <http://bugs.buildroot.net/> for instructions.
>> >> Makefile:213: recipe for target 'lib/xmlparse.lo' failed
>> >> make[1]: *** [lib/xmlparse.lo] Error 1
>> >> make[1]: *** Waiting for unfinished jobs....
>> >> make[1]: Leaving directory '/home/administrator/Downloads
>> /buildroot_2017/
>> >> buildroot-2017.02.5/output/build/expat-2.2.2'
>> >> package/pkg-generic.mk:216: recipe for target '/home/administrator/
>> >> Downloads/buildroot_2017/buildroot-2017.02.5/output/
>> >> build/expat-2.2.2/.stamp_built' failed
>> >> make: *** [/home/administrator/Downloads/buildroot_2017/
>> >> buildroot-2017.02.5/output/build/expat-2.2.2/.stamp_built] Error 2
>> > I reproduced the exact same issue here on current master as of
>> c2da653d085df1.
>> > I only run 'make expat' to shorten build time.
>> >
>> > I think you should to take this to the gcc bug tracker. I don't think
>> any of
>> > the Buildroot gcc patches have anything to do with that, but I'll let
>> the
>> > toolchain experts on the list share their opinion.
>>
>>  I didn't check but I indeed doubt that any of Buildroot's gcc patches
>> could
>> have anything to do with it.
>>
>>  To be able to report it to the gcc bug tracker, it would have to be
>> reproduced
>> with current gcc master and with a minimal piece of code that exposes the
>> bug.
>> Quite a bit of work...
>>
>>  Aseem, to unblock you, I think it's best if you just use the much better
>> tested
>> and compatible arm926t CPU choice. It will result in slightly less
>> efficient
>> code because it won't make use of the iwmmx2 instructions, but I doubt
>> that it
>> will have more than a few % performance impact on generic programs.
>>
>>  Regards,
>>  Arnout
>>
>> --
>> Arnout Vandecappelle                          arnout at mind be
>> Senior Embedded Software Architect            +32-16-286500
>> Essensium/Mind                                http://www.mind.be
>> G.Geenslaan 9, 3001 Leuven, Belgium           BE 872 984 063 RPR Leuven
>> LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
>> GPG fingerprint:  7493 020B C7E3 8618 8DEC 222C 82EB F404 F9AC 0DDF
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20170823/836548bd/attachment.html>