From: Ni Qingliang <niqingliang@insigma.com.cn>
To: McClintock Matthew-B29882 <B29882@freescale.com>,
"Patches and discussions about the oe-core layer"
<openembedded-core@lists.openembedded.org>
Cc: Andrei Gherzan <andrei@gherzan.ro>,
Andrei Gherzan <andrei.gherzan@windriver.com>
Subject: Re: [PATCH] busybox: defconfig modified in order to activate CONFIG_EXPR_MATH_SUPPORT_64
Date: Mon, 9 Jan 2012 14:06:41 +0800 [thread overview]
Message-ID: <1326089201.27569.10.camel@localhost.localdomain> (raw)
In-Reply-To: <CAEsOVNeAuF5u2J_MhZg9tVezexCNyK2rGsZ2sUgBpTeJ90ZVqw@mail.gmail.com>
indeed, I think maybe providing specific config file for specific
machine is better, but not spliting the config to fragments.
On Mon, 2012-01-09 at 13:08 +0800, McClintock Matthew-B29882 wrote:
> Is anyone working on more fine grained control of busybox? Some ideas include:
>
> 1) configure via PACKAGECONFIG?
>
> 2) supply a defconfig for busybox?
>
> 3) multiple busybox recipes?
>
> -M
>
> On Sun, Jan 8, 2012 at 6:03 PM, Andrei Gherzan <andrei@gherzan.ro> wrote:
> > From: Andrei Gherzan <andrei.gherzan@windriver.com>
> >
> > Enable 64-bit math support in the expr applet. This will make
> > the applet slightly larger, but will allow computation with very
> > large numbers.
> >
> > [YOCTO #1767]
> >
> > Signed-off-by: Andrei Gherzan <andrei@gherzan.ro>
> > ---
> > meta/recipes-core/busybox/busybox-1.19.3/defconfig | 2 +-
> > 1 files changed, 1 insertions(+), 1 deletions(-)
> >
> > diff --git a/meta/recipes-core/busybox/busybox-1.19.3/defconfig b/meta/recipes-core/busybox/busybox-1.19.3/defconfig
> > index 1990f28..ebd751d 100644
> > --- a/meta/recipes-core/busybox/busybox-1.19.3/defconfig
> > +++ b/meta/recipes-core/busybox/busybox-1.19.3/defconfig
> > @@ -214,7 +214,7 @@ CONFIG_FEATURE_ENV_LONG_OPTIONS=y
> > # CONFIG_EXPAND is not set
> > # CONFIG_FEATURE_EXPAND_LONG_OPTIONS is not set
> > CONFIG_EXPR=y
> > -# CONFIG_EXPR_MATH_SUPPORT_64 is not set
> > +CONFIG_EXPR_MATH_SUPPORT_64=y
> > CONFIG_FALSE=y
> > # CONFIG_FOLD is not set
> > # CONFIG_FSYNC is not set
> > --
> > 1.7.5.4
> >
> >
> > _______________________________________________
> > Openembedded-core mailing list
> > Openembedded-core@lists.openembedded.org
> > http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
>
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
--
Yi Qingliang
niqingliang@insigma.com.cn
https://niqingliang2003.wordpress.com
next prev parent reply other threads:[~2012-01-09 6:15 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-09 0:03 [PATCH] busybox: defconfig modified in order to activate CONFIG_EXPR_MATH_SUPPORT_64 Andrei Gherzan
2012-01-09 5:08 ` McClintock Matthew-B29882
2012-01-09 6:06 ` Ni Qingliang [this message]
2012-01-09 8:09 ` Phil Blundell
2012-01-09 16:26 ` Mark Hatle
2012-01-09 16:52 ` Otavio Salvador
2012-01-13 15:12 ` Darren Hart
2012-01-12 20:23 ` Saul Wold
2012-01-13 7:07 ` Lauri Hintsala
2012-01-13 8:16 ` Andrei Gherzan
2012-01-13 9:50 ` Lauri Hintsala
2012-01-19 18:31 ` Saul Wold
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1326089201.27569.10.camel@localhost.localdomain \
--to=niqingliang@insigma.com.cn \
--cc=B29882@freescale.com \
--cc=andrei.gherzan@windriver.com \
--cc=andrei@gherzan.ro \
--cc=openembedded-core@lists.openembedded.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox