From: Kang Kai <Kai.Kang@windriver.com>
To: Mark Hatle <mark.hatle@windriver.com>
Cc: "poky@yoctoproject.org" <poky@yoctoproject.org>,
Patches,
about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: Question about apply eglibc configurability to create minimal image
Date: Fri, 10 Jun 2011 10:50:19 +0800 [thread overview]
Message-ID: <4DF1866B.7010106@windriver.com> (raw)
In-Reply-To: <4DF0E4A8.1000608@windriver.com>
Hi Mark,
Thank you very much for your detailed comments.
>
> From the above, I'm pretty sure that "netbase" will require a lot of networking
> components, specifically adding things like libc-inet. So avoid netbase.
>
> It's possible that keyboard/keymaps may cause additional stuff to come in due to
> locale requirements.. so I'd dump those as well..
>
> sysvinit may also introduce some additional items -- so if it causes problems,
> remove it and switch to the init located within busybox.
sysvinit and busybox, tinilogin require eglibc libc-crypt support.
And busybox need libnsl, so I try to finger out how to break these
depencies.
> update-alternatives is what included gettext -- so this might need some
> enhancement to avoid gettext as a requirement. So I'd suggest skipping it.
> (Note without it, it's likely busybox, tinylogin may not get setup properly...)
I will test it.
> udev is quite complex and drags in a number of components -- so drop that..
RP suggested using mdev provided by busybox instead, I'll do it later.
> Leaving:
>
> base-files \
> base-passwd \
> busybox \
> initscripts \
> modutils-initscripts \
> sysvinit \
> tinylogin
>
> First see if you can compile the above with a minimal eglibc configuration. If
> not I can help you work through those issues.. If you can, you SHOULD see a
> fairly dramatic decrease in size.
First of all, I do the minimal with your direction and give you feedback.
> --Mark
Thank & Regards,
Kai
>> Thanks a lot!
>>
>> I made a mistake that try eglibc configurability in a directory which
>> has build core-image-minimal, so the packages which depend on eglibc
>> didn't rebuild, and I didn't find the dependency before. I am sorry!
>>
>> Regards,
>> Kai
next prev parent reply other threads:[~2011-06-10 2:53 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4DF0A70C.7080501@windriver.com>
2011-06-09 10:59 ` [poky] Question about apply eglibc configurability to create minimal image Koen Kooi
2011-06-09 15:20 ` Mark Hatle
2011-06-09 15:34 ` Frans Meulenbroeks
2011-06-09 15:38 ` Mark Hatle
2011-06-10 2:50 ` Kang Kai [this message]
2011-06-17 10:05 ` Kang Kai
2011-06-17 15:46 ` Mark Hatle
2011-06-17 16:10 ` Koen Kooi
2011-06-21 7:35 ` Kang Kai
2011-06-27 2:09 ` Kang Kai
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=4DF1866B.7010106@windriver.com \
--to=kai.kang@windriver.com \
--cc=mark.hatle@windriver.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=poky@yoctoproject.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