From: Gary Thomas <gary@mlbassoc.com>
To: Poky <poky@lists.pokylinux.org>
Subject: eglibc configurability
Date: Mon, 07 Feb 2011 07:44:05 -0700 [thread overview]
Message-ID: <4D500535.3070505@mlbassoc.com> (raw)
I often run small (slow) embedded systems with only a ramdisk
based file system. When I use Poky for this, one side effect
is that some packages need to be "configured" on bootup, which
in the case of a ramdisk based operation means every time.
I notice that the eglibc package brings in a couple of these
which are problematic (mostly in how long they take to run)
Looking at meta/conf/distro/include/poky-eglibc.inc:
LIBC_DEPENDENCIES = "libsegfault \
eglibc \
eglibc-dbg \
eglibc-dev \
eglibc-utils \
eglibc-thread-db \
eglibc-localedata-i18n \
eglibc-gconv-ibm850 \
eglibc-gconv-cp1252 \
eglibc-gconv-iso8859-1 \
eglibc-gconv-iso8859-15 \
locale-base-en-us \
locale-base-en-gb "
On my OMAP-L138 target, configuring locale-base-* takes
a long time, upwards of 35 seconds each.
Are multiple locale-base packages really necessary?
How could I best (in the Poky spirit) limit this? In the
minimum, I'd like to only have one locale, saving at least
35 seconds of boot time.
Ideas? Comments?
Thanks
--
------------------------------------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
------------------------------------------------------------
next reply other threads:[~2011-02-07 14:44 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-07 14:44 Gary Thomas [this message]
2011-02-07 15:45 ` eglibc configurability Kamble, Nitin A
2011-02-07 15:54 ` Gary Thomas
2011-02-07 16:06 ` Richard Purdie
2011-02-07 16:19 ` Gary Thomas
2011-02-07 16:29 ` Mark Hatle
2011-02-07 16:54 ` Gary Thomas
2011-02-07 16:57 ` Richard Purdie
2011-02-07 17:04 ` Mark Hatle
2011-02-07 17:57 ` Gary Thomas
2011-02-07 19:09 ` Mark Hatle
2011-02-07 16:55 ` Richard Purdie
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=4D500535.3070505@mlbassoc.com \
--to=gary@mlbassoc.com \
--cc=poky@lists.pokylinux.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 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.