On Tue, Aug 7, 2012 at 1:10 PM, Elvis Dowson <elvis.dowson@...> wrote:

Hi,

       I decided to modify the bash and busybox recipes to build

statically, and try to create a core-image-minimal root filesystem, so that

I can get a sensible prompt with paths set, etc, to debug the dynamic

linking issue.

Just copying a static bash binary to the root of the ramdisk image and

specifying init=/bash didn't work for a static bash+core-image-minimal root

filesystem, it aborts with a panic. If I have only the bash executable in

the ramdisk and nothing else, it displays the bash prompt.

Now, I've noticed something weird during core-image-minimal image

generation.

When I build the static versions of bash, the size of the binary is 8MB, but

when I explore the binary in the tar.gz image or extract it to my ramdisk,

it shows as being only 1.6MB.

How can there be a difference between the statically built bash file

/tool/yocto/poky/build/tmp/work/ppc440-poky-linux/bash-4.2-r4/image/bin/bash

(8MB)

and in the file contained in the core-image-minimal-virtex-5.tar.gz

/bin/bash (1.6MB)

I'm seeing the same discrepancy for busybox

/tool/yocto/poky/build/tmp/work/ppc440-poky-linux/busybox-1.19.4-r18/image/bin/busybox

(8.2 MB)

and in the generate rootfs image

/bin/busybox (1.4MB)

This shouldn't happen, right?

I assume they are stripped in case where they are smaller.