Image size explosion

Image size explosion

[Gary Thomas]

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.

Thanks

-- 
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------

Re: Image size explosion

[Richard Purdie]

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...

Cheers,

Richard

Re: Image size explosion

[Gary Thomas]

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
------------------------------------------------------------

Re: Image size explosion

[Holger Hans Peter Freyther]

On 07/05/2011 11:44 PM, Gary Thomas wrote:

> 
> I just updated against the latest master and rebuilt and now my images
> are back to a more sane size.

I have posted a udev (libgudev ends in the wrong package, pulling in
glib/gthread/gio/gmodule/gobject) fix to the OE ml, it might apply to you too.

holger