@knc1: I (almost) never *completely* link statically. At best I statically link one or two troublesome or recent lib, but I usually try to use mostly dynamic linking, while avoiding ABI/API mismatches, (like this one, which wouldn't even be an issue if I was building against the same glibc as the Kindle, which is what I'm doing on my K5 TC
).
In the xz case, I end up with a ~160K binary with NEEDED entries for libgcc_s.so.1 @ GCC_3.5, libpthread.so.0 & libc.so.6 @ GLIBC_2.4, which should be more than backward compatible enough to run on the K2/K3
.