From: ChenQi <Qi.Chen@windriver.com>
To: Paul Eggleton <paul.eggleton@linux.intel.com>
Cc: qingtao.cao@windriver.com, "Hart,
Darren" <dvhart@linux.intel.com>,
poky@yoctoproject.org
Subject: Re: [PATCH 1/2] poky-tiny.conf: add extra libc features
Date: Wed, 10 Jul 2013 17:12:20 +0800 [thread overview]
Message-ID: <51DD2574.7060608@windriver.com> (raw)
In-Reply-To: <5822283.x6sXiXjJIc@helios>
On 07/10/2013 04:30 PM, Paul Eggleton wrote:
> Hi Qi / Darren,
>
> On Wednesday 10 July 2013 14:37:12 Qi.Chen@windriver.com wrote:
>> From: Chen Qi <Qi.Chen@windriver.com>
>>
>> Add two extra libc features, libc-spawn and libc-rcmd, as they are
>> needed to successfully compile the shadow package which is needed
>> if we set USER_GROUP_SETTIGNS in some configuration file.
>>
>> [YOCTO #4074]
>>
>> Signed-off-by: Chen Qi <Qi.Chen@windriver.com>
>> ---
>> meta-yocto/conf/distro/poky-tiny.conf | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/meta-yocto/conf/distro/poky-tiny.conf
>> b/meta-yocto/conf/distro/poky-tiny.conf index 755667f..9d9ea3c 100644
>> --- a/meta-yocto/conf/distro/poky-tiny.conf
>> +++ b/meta-yocto/conf/distro/poky-tiny.conf
>> @@ -62,7 +62,7 @@ ASSUME_PROVIDED += "pkgconfig$"
>>
>> # Reconfigure eglibc for a smaller installation
>> # Comment out any of the lines below to disable them in the build
>> -DISTRO_FEATURES_LIBC_TINY = "libc-libm libc-crypt"
>> +DISTRO_FEATURES_LIBC_TINY = "libc-libm libc-crypt libc-spawn libc-rcmd"
>> DISTRO_FEATURES_LIBC_TINY_append_x86-64 = " libc-libm-big"
>>
>> # Required for "who"
> Is this really appropriate for poky-tiny? It seems to me it might be
> orthogonal to the point of poky-tiny which is to be pretty much as light as
> possible.
>
> Cheers,
> Paul
>
I added these two extra libc features because I wanted
USER_GROUP_SETTINGS to have effect for poky-tiny.
For now, because of lack of libc features, adding packages to poky-tiny
is likely to fail.
So the question here is, are we deciding that poky-tiny equals to
'limited-featured libc + tiny init + busybox"? If so, maybe we need to a
mechanism to warn user when they try to add packages to poky-tiny.
Besides, removing the libc features doesn't seem to have significant
effects on the size of the image.
chenqi@pek-qchen1-d1:~/poky$ ls -lh
build-tiny/tmp/work/qemux86-poky-linux/core-image-minimal/1.0-r0/rootfs/lib/libc-2.17.so
-rwxr-xr-x 1 chenqi chenqi 1.1M Jul 10 13:49
build-tiny/tmp/work/qemux86-poky-linux/core-image-minimal/1.0-r0/rootfs/lib/libc-2.17.so
chenqi@pek-qchen1-d1:~/poky$ ls -lh
build/tmp/work/qemux86-poky-linux/core-image-minimal/1.0-r0/rootfs/lib/libc-2.17.so
-rwxr-xr-x 1 chenqi chenqi 1.5M Jul 3 11:23
build/tmp/work/qemux86-poky-linux/core-image-minimal/1.0-r0/rootfs/lib/libc-2.17.so
Best Regards,
Chen Qi
next prev parent reply other threads:[~2013-07-10 9:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <cover.1373438138.git.Qi.Chen@windriver.com>
2013-07-10 6:37 ` [PATCH 1/2] poky-tiny.conf: add extra libc features Qi.Chen
2013-07-10 8:30 ` Paul Eggleton
2013-07-10 9:12 ` ChenQi [this message]
2013-07-10 17:33 ` Darren Hart
2013-07-10 19:58 ` Saul Wold
2013-07-11 2:50 ` ChenQi
2013-07-10 6:39 ` [PATCH 2/2] local.conf.sample.extended: add USER_GROUP_SETTINGS Qi.Chen
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=51DD2574.7060608@windriver.com \
--to=qi.chen@windriver.com \
--cc=dvhart@linux.intel.com \
--cc=paul.eggleton@linux.intel.com \
--cc=poky@yoctoproject.org \
--cc=qingtao.cao@windriver.com \
/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.