@brianinmaine: Wanting to link against "the Kindle's libraries" is a good idea in theory, but in practice, the libraries (at link-time) don't dictate much, the headers do, and amazon doesn't ship headers in their FW (not unlike a binary Linux distro, which is why you have a -dev/-devel package for each package)
.
So, if you *really* want to link against the same stuff, you'll need to replicate the Kindle sysroot *with* the development files (the headers). (ie. cross-compile the exact same versions of what you care about as the device you target).
Fortunately for us, we can get away with building against newer/older stuff, as long as we're building against something that is ABI compatible with what the Kindle runs. That's where API/ABI, sover & symbol versionning come into play, and you start to dig into the inner workings of the ELF binary format.