[Buildroot] ARM default configuration

[Buildroot] ARM default configuration

[Alexander Sirotkin]

What ARM default configurations are supposed to work ? I tried a few,
including  integrator926_defconfig, but none of them compiled.
Or maybe I do not understand the idea of default configuration. Isn't it
supposed to compile without errors and without asking the user for input ?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20100427/bbf0bf4b/attachment.htm>

[Buildroot] ARM default configuration

[Rob Alley]

> What ARM default configurations are supposed to work ? I tried a few,
including  integrator926_defconfig, but none of them compiled. 
> Or maybe I do not understand the idea of default configuration. Isn't
it supposed to compile without errors and without asking the user for
input ?

I believe they are all **supposed** to work.  The at91sam9260 and
at91sam9g20 defconfigs work for me.  You may still be prompted for user
inputs the first time - buildroot is constantly being updated but the
default configs get left behind, this results in prompting for new
packages etc.
 
Rob.

[Buildroot] ARM default configuration

[Alexander Sirotkin]

On Wed, Apr 28, 2010 at 1:39 AM, Rob Alley <Rob.Alley@navmanwireless.com>wrote:

> > What ARM default configurations are supposed to work ? I tried a few,
> including  integrator926_defconfig, but none of them compiled.
> > Or maybe I do not understand the idea of default configuration. Isn't
> it supposed to compile without errors and without asking the user for
> input ?
>
> I believe they are all **supposed** to work.  The at91sam9260 and
> at91sam9g20 defconfigs work for me.  You may still be prompted for user
> inputs the first time - buildroot is constantly being updated but the
> default configs get left behind, this results in prompting for new
> packages etc.
>
>
 at91sam9260dfc_defconfig fails with the following error:
/home/sashas/buildroot-2010.02/output/staging/usr/bin/arm-linux-uclibc-ld:
error
:
/home/sashas/buildroot-2010.02/output/staging/usr/bin-ccache/../lib/gcc/arm-li
nux-uclibc/4.3.4/libgcc.a(_ashrdi3.o) uses hardware FP, whereas u-boot uses
soft
ware FP


> Rob.
>
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20100428/ac9926b4/attachment.htm>

[Buildroot] ARM default configuration

[Ravi Kumar Kulkarni]

On Wed, Apr 28, 2010 at 5:54 PM, Alexander (Sasha) Sirotkin
<buildroot@browserseal.com> wrote:
>
>
> On Wed, Apr 28, 2010 at 1:39 AM, Rob Alley <Rob.Alley@navmanwireless.com>
> wrote:
>>
>> > What ARM default configurations are supposed to work ? I tried a few,
>> including ?integrator926_defconfig, but none of them compiled.
>> > Or maybe I do not understand the idea of default configuration. Isn't
>> it supposed to compile without errors and without asking the user for
>> input ?
>>
>> I believe they are all **supposed** to work. ?The at91sam9260 and
>> at91sam9g20 defconfigs work for me. ?You may still be prompted for user
>> inputs the first time - buildroot is constantly being updated but the
>> default configs get left behind, this results in prompting for new
>> packages etc.
>>
>
> ?at91sam9260dfc_defconfig fails with the following error:
> /home/sashas/buildroot-2010.02/output/staging/usr/bin/arm-linux-uclibc-ld:
> error
> :
> /home/sashas/buildroot-2010.02/output/staging/usr/bin-ccache/../lib/gcc/arm-li
> nux-uclibc/4.3.4/libgcc.a(_ashrdi3.o) uses hardware FP, whereas u-boot uses
> soft
> ware FP
>

when u make defconfig the toolchain selects hardware floating point by
default . so
so go to  make menuconfig
and select  toolchain->use software floating point by default . tat
will solve problem.
warm regards,
Ravi Kulkarni.

[Buildroot] ARM default configuration

[Alexander Sirotkin]

On Wed, Apr 28, 2010 at 4:28 PM, Ravi Kumar Kulkarni
<ravilinux4u@gmail.com>wrote:

> On Wed, Apr 28, 2010 at 5:54 PM, Alexander (Sasha) Sirotkin
> <buildroot@browserseal.com> wrote:
> >
> >
> > On Wed, Apr 28, 2010 at 1:39 AM, Rob Alley <Rob.Alley@navmanwireless.com
> >
> > wrote:
> >>
> >> > What ARM default configurations are supposed to work ? I tried a few,
> >> including  integrator926_defconfig, but none of them compiled.
> >> > Or maybe I do not understand the idea of default configuration. Isn't
> >> it supposed to compile without errors and without asking the user for
> >> input ?
> >>
> >> I believe they are all **supposed** to work.  The at91sam9260 and
> >> at91sam9g20 defconfigs work for me.  You may still be prompted for user
> >> inputs the first time - buildroot is constantly being updated but the
> >> default configs get left behind, this results in prompting for new
> >> packages etc.
> >>
> >
> >  at91sam9260dfc_defconfig fails with the following error:
> >
> /home/sashas/buildroot-2010.02/output/staging/usr/bin/arm-linux-uclibc-ld:
> > error
> > :
> >
> /home/sashas/buildroot-2010.02/output/staging/usr/bin-ccache/../lib/gcc/arm-li
> > nux-uclibc/4.3.4/libgcc.a(_ashrdi3.o) uses hardware FP, whereas u-boot
> uses
> > soft
> > ware FP
>
Thanks. I know how to fix it. I was just trying to make a point that most of
the default configurations do not work.

> >
>
> when u make defconfig the toolchain selects hardware floating point by
> default . so
> so go to  make menuconfig
> and select  toolchain->use software floating point by default . tat
> will solve problem.
> warm regards,
> Ravi Kulkarni.
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20100428/bad458db/attachment.htm>