Results with glibc-2.2.92

[Dan Kegel]

Jeff Chua wrote:
> > > So, why does the gcc/glib not default to "strip" during installation?
> > > Most people don't bother with these files after install.
> >
> > The extra size doesn't add a bit to the runtime costs.  But the debug
> > info is invaluable when you need it.  If you then strip the binaries it
> > is too late.
> 
> I ran into a problem trying to build a minimum filesystem using
> initrd/ramdisk and realized that the bin and lib are too big to fit into
> initrd ... there seems to be a limitation of <4MB for celeron and <8M for
> pentium to boot, so stripping these files make it easier to fit the
> necessary tools into the limited fs.

I run into this situation, too; what I do is strip all the files
on their way into the init boot image.  The original binaries
remain unstripped.  That way I can do gdbserver on the
stripped binary with gdb on the unstripped binary.

BTW normal binaries, if stripped with strip -g, are still
bloated; you have to do strip --remove-unneeded.  (Is that a
bug in strip?)  
Kernel modules should be stripped with -g, because they
don't work if stripped with --remove-unneeded.

- Dan