+
+ To conserve bytes it's good to know where they're being used, and the + size of the final executable isn't always a reliable indicator of + the size of the components (since various structures are rounded up, + so a small change may not even be visible by itself, but many small + savings add up). +
++ To examine a busybox binary with an eye to saving bytes, build an + optimized debug version and run the "nm" command against it, like so: +
++ make clean && make STRIPCMD=/bin/true && nm --size-sort busybox +
++ This gives a list of symbols and the amount of space allocated for + each one, sorted by size. (Note: do not enable CONFIG_DEBUG for this, + as that disables compiler optimization which is great for running gdb + but misleading when trying to figure out how much space each component + is really using under normal circumstances.) +
+