Since it is now the default rescue shell, busybox should probably default to be statically linked.
It is static linked. USE=static is pretty much obsolete for busybox a relic of before bb became the rescue shell. The way it works right now is if you have USE=static set bb and busybox will both be static. If USE=static is not set then the ebuild builds a static and dynamic copy of busybox. The static copy is /bin/bb and when invoked you will be in the ash shell where all other applets are. Otherwise run the dynamic copy /bin/busybox to see the applets and invoke busybox the standard way. Maybe in reality we should just remove the USE=static all together.
Ah great. In a desperate hope to make this bug useful, should that explanation be added as einfo's?
(In reply to comment #1) > Maybe in reality we should just remove the USE=static all together. Yup - I have changed the summary accordingly.
blubb@aqua ~ $ ldd /bin/bb libm.so.6 => /lib/libm.so.6 (0x000000313b100000) libcrypt.so.1 => /lib/libcrypt.so.1 (0x000000313f600000) libc.so.6 => /lib/libc.so.6 (0x000000313ac00000) /lib64/ld-linux-x86-64.so.2 (0x000000313a000000) blubb@aqua ~ $ file /bin/bb /bin/bb: ELF 64-bit LSB executable, AMD x86-64, version 1 (SYSV), for GNU/Linux 2.6.5, dynamically linked (uses shared libs), stripped /me hmms...
chances are good your glibc sucks, see Bug 94879 either way, unrelated to this bug
we'll revisit this when we can specify default USE flags on a per-ebuild basis