Skip to contentSkip to conversation

Image size explosion

DISCUSSION Gary Thomas 3 participants 4 messages Jul 5, 2011

lore
Share & tools
lore
#0 lore raw

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

Signature · 4 lines
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------
#1 lore raw
Quoted 16 lines · 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.

Quoted 4 lines

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

#2 lore raw
Quoted 22 lines · Richard Purdie
Quoted 16 lines · 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.

Quoted 4 lines

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.

Quoted 5 lines

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

Signature · 4 lines
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------
#3 lore raw
Quoted 3 lines · Gary Thomas

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