View Single Post
Old 08-20-2012, 10:45 PM   #34
NiLuJe
BLAM!
NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.
 
NiLuJe's Avatar
 
Posts: 5,250
Karma: 5189261
Join Date: Jun 2010
Location: Paris, France
Device: Kindle 2i, 3g, 4, 5w, PW & PW2; Kobo H2O
@twobob/knc1: Yeah, the glibc's ABI backwards compatibility has been pretty solid, in my experience, without too much burden . That's why your current binaries should work with the Kindle's newer glibc. (Keep in mind that glibc isn't only libc.so, though, there a whole bunch of other core library in there: libm, libcrypt and libdl being the most prominent of those).

For a stark comparison, libstdc++ is a whole different kettle of fish. There *is* ABI compatibility, but there have been so much change in the API over the years that you usually *need* to ship it/static link it to make sure it won't blow up, especially on older systems...
There's still a libstdc++-v3 package available in nearly every distro out there to provide support for older dynamically linked binary/proprietary C++ apps for this very reason.

Last edited by NiLuJe; 08-20-2012 at 10:51 PM.
NiLuJe is offline   Reply With Quote