From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2] package/uclibc: Enable wordexp functionality
Date: Tue, 21 Mar 2017 18:23:06 +0200 [thread overview]
Message-ID: <1490113386.19767.140.camel@linux.intel.com> (raw)
In-Reply-To: <20170321171710.79befd08@free-electrons.com>
On Tue, 2017-03-21 at 17:17 +0100, Thomas Petazzoni wrote:
> Hello,
>
> On Tue, 21 Mar 2017 18:11:48 +0200, Andy Shevchenko wrote:
>
> > > ?I.e the
> > > size of uClibc without/with this option enabled, for example on
> > > ARM???
> >
> > No, I have no ARM board to test this. Or you mean to built entire
> > stack
> > what I'm using for some arbitrary ARM board?
>
> You don't need a ARM board. Just make a Buildroot build for ARM with
> uClibc (wordexp disabled), look at the uClibc size, and then the same
> build but this time with your patch applied (which enables wordexp).
Got it.
Will do when will have time later this week.
--
Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Intel Finland Oy
next prev parent reply other threads:[~2017-03-21 16:23 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-21 16:02 [Buildroot] [PATCH v2] package/bluez5_utils: Allow user to enable disabled plugins Andy Shevchenko
2017-03-21 16:02 ` [Buildroot] [PATCH v2] package/uclibc: Enable wordexp functionality Andy Shevchenko
2017-03-21 16:06 ` Thomas Petazzoni
2017-03-21 16:11 ` Andy Shevchenko
2017-03-21 16:17 ` Thomas Petazzoni
2017-03-21 16:23 ` Andy Shevchenko [this message]
2017-03-21 16:28 ` Baruch Siach
2017-04-09 4:32 ` Waldemar Brodkorb
2017-04-09 7:42 ` Thomas Petazzoni
2017-03-21 19:53 ` Waldemar Brodkorb
2017-04-16 14:29 ` Waldemar Brodkorb
2017-04-29 12:26 ` Thomas Petazzoni
2017-03-21 16:02 ` [Buildroot] [PATCH v2] Revert "bluez5_utils: not available with uClibc" Andy Shevchenko
2017-03-21 17:01 ` [Buildroot] [PATCH v2] package/bluez5_utils: Allow user to enable disabled plugins Peter Korsgaard
2017-03-21 17:06 ` Andy Shevchenko
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=1490113386.19767.140.camel@linux.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=buildroot@busybox.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.