glibc........ memory limitations.... ideas?

kd at kd at
Thu Oct 21 01:16:38 EST 1999


I have a small question...

We are developing an embedded solution as most of the people here on the
list. This means that we (or at least I) are limited be the amount of
available memory in the units.
We for example are limited by a 2 MB flash chip that might someday be 4MB.
In maybe 1.2MB of this chip I can stuff applications that need to run on
the device.
A statically linked application (with glibc) is arround 300KB (250KB
-450KB).  which means that I can stuff maybe 3-4 statically linked
applications in the flash.

The othre option is to link the applications dinamically to glibc and
stdlibc++. is around 4 MB and stdlibc++ is around 2.5 MB. So
using dinamically linked
applications  is not even a possibility when you look at it. BTW : Why are
thes libraries so huge!?

Compressed filesystems is one option but that means we have to increase the
size of the DRAM and that again means increased current drain. Limited
battery resources is
one of our contraints also.

How do you guys cram all the software you want into so small space? Are
there any othre c and c++ libraries that are smaller but provides access to
threads (pthreads) and
work with linux?

Thanks, for all inputs.


** Sent via the linuxppc-embedded mail list. See

More information about the Linuxppc-embedded mailing list