When building the client-side (ram kernel, Kindle-side) of the ATK source code package, you should be using a gcc cross-compile tool chain configured for building "Standalone" applications.
A "Standalone" application does not reference a system C library.
A "Hosted" application does reference a system C library.
Both tool-chains (for either Linux or Windows) are indexed in the KeK Reference Manual, at:
http://knetconnect.com/KeK/KeK_refer...bsection-B.1.2
You probably want both the -56 and the -57 builds.
When you unpack them, they will both create an "arm-2012.03" parent directory . . .
Although it should be possible to unpack both of them into that same file system tree, to ease future maintenance, I put them each into their own file system tree.
Unpack the -57 archive at the desired location on your system (typically /opt), then rename the parent directory: arm-2012.03-glibc
Then unpack the -56 archive at the desired location on your system (typically /opt), then rename the parent directory:
arm-2012.03-elf
A couple of notes for those building the ATK source under M$-Windows . . .
The ATK project files and make files assume a cygwin environment, but the above tool chains are "Windows Native" tool chains.
You can drop all references to cygwin in the Freescale project.
You can also drop all references to the cygwin tool chain components (such as: objcopy), because you just installed a much more recent "Windows Native" build of binutils.
The ATK source code bundle, as shipped, was using a gcc-4.1.1 based tool chain. You just installed a gcc-4.6 based tool chain.
GCC-4.6 is
much more strict about the source code than GCC-4.1, meaning you may find more errors and warnings during the build which will require tweaking (correcting) the Freescale sources.
Enjoy.