From a K3, which, IIRC, is similar to what we're talking about here:
Code:
[root@kindle root]# /lib/libc.so.6
GNU C Library stable release version 2.5, by Roland McGrath et al.
Copyright (C) 2006 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.
There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A
PARTICULAR PURPOSE.
Compiled by GNU CC version 4.1.2.
Compiled on a Linux 2.6.15 system on 2008-06-10.
Available extensions:
crypt add-on version 2.1 by Michael Glad and others
GNU Libidn by Simon Josefsson
GNU libio by Per Bothner
NIS(YP)/NIS+ NSS modules 0.19 by Thorsten Kukuk
Native POSIX Threads Library by Ulrich Drepper et al
Support for some architectures added on, not maintained in glibc core.
BIND-8.2.3-T5B
Thread-local storage support included.
For bug reporting instructions, please see:
<http://www.gnu.org/software/libc/bugs.html>.
[root@kindle root]# uname -a
Linux kindle 2.6.26-rt-lab126 #5 Sat Sep 1 14:28:26 PDT 2012 armv6l unknown
[root@kindle root]# cat /proc/cpuinfo
Processor : ARMv6-compatible processor rev 3 (v6l)
BogoMIPS : 511.18
Features : swp half thumb fastmult vfp edsp java
CPU implementer : 0x41
CPU architecture: 6TEJ
CPU variant : 0x1
CPU part : 0xb36
CPU revision : 3
Cache type : write-back
Cache clean : cp15 c7 ops
Cache lockdown : format C
Cache format : Harvard
I size : 16384
I assoc : 4
I line length : 32
I sets : 128
D size : 16384
D assoc : 4
D line length : 32
D sets : 128
Hardware : Amazon MX35 Luigi Board
Revision : 35020
Serial : "B006XXXXXXXXXXXX"
BoardId : "SP1B000000000000"
Except the kernel might be even older on 2.x, I build w/ 2.6.22 as a minimum.
Basically, if you intend to use a decent GCC version, the biggest hassle is the tremendously old glibc (and, depending on what you build, the sometimes wonky old kernel headers might come into play). Which is why my TC is built against glibc 2.9, and I mess with the FLAGS to make sure nothing too new gets pulled.
(That was mostly out of fear that glibc 2.5(.1) wouldn't build with a recent GCC, a fear which might actually be completely baseless [and/or easy to patch], but I've never bothered to look into it, because what I've been doing WorksForMe(TM)
).