From: Gary Thomas <gary@mlbassoc.com>
To: Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: Poky Project <poky@yoctoproject.org>
Subject: Re: Image size explosion
Date: Tue, 05 Jul 2011 15:44:18 -0600 [thread overview]
Message-ID: <4E1385B2.7050405@mlbassoc.com> (raw)
In-Reply-To: <1309884260.20015.727.camel@rex>
On 07/05/2011 10:44 AM, Richard Purdie wrote:
> On Tue, 2011-07-05 at 10:29 -0600, Gary Thomas wrote:
>> I just rebuilt my image after updating to the latest master and
>> I observed image explosion (my mimimal image went from 3.9MB to
>> 37MB!) Looking at what went into the image, I see some packaging
>> changes. The package
>> libc6
>> is now a bunch of packages
>> eglibc
>> eglibc-dev
>> eglibc-extra-nss
>> libcidn1
>> libgcc1
>> libgcc-s-dev
>> libthread-dbl
>> linux-libc-headers-dev
>> which seem to be responsible for the bloat.
>>
>> Questions:
>> * What changed that now brings this in?
>> * Can I get back to my old, minimal, setup? This is for a deeply
>> embedded device and I don't need/want any development stuff.
>
> When we split up the locale generation we broke eglibc. It sounds like
> you're missing the fixes for that?
>
> Assuming minimal stops pulling in eglibc-dev things should look
> better...
I just updated against the latest master and rebuilt and now my images
are back to a more sane size.
Thanks
--
------------------------------------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
------------------------------------------------------------
next prev parent reply other threads:[~2011-07-05 21:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-05 16:29 Image size explosion Gary Thomas
2011-07-05 16:44 ` Richard Purdie
2011-07-05 21:44 ` Gary Thomas [this message]
2011-07-05 22:43 ` Holger Hans Peter Freyther
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=4E1385B2.7050405@mlbassoc.com \
--to=gary@mlbassoc.com \
--cc=poky@yoctoproject.org \
--cc=richard.purdie@linuxfoundation.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.