That first step, installing bootstrap glibc headers, is a new
and annoying prerequisite as of gcc-3.3. See
http://sources.redhat.com/ml/crossgcc/2003-06/msg00170.html
for my rant on the subject.
ACK.
_But_ it's even worse that there's no[1] strict documentation on how to
get a working cross-compiler. There are some "interesting"
configurations which should have easily findable documentation.
(Extensive --with-sysroot docs?).
For me, toying mostly with around with Linux, my top wishlist is:
- Building a Linux kernel-only cross compiler on my i386-linux
box for some {mips|ppc|m68k|...}-linux target running
efficiently on the box I build it on (BUILD == HOST).
- Building a Linux kernel-only cross compiler on my i386-linux
box for some {mips|ppc|m68k|...}-linux target running
on any i386-like Linux machine (BUILD != HOST). So I can
easily copy this binutils/compiler suite to some other box.
- Building a full cross compiler (including userland and all
sensefull languages) with BUILD == HOST as well as BULID !=
HOST, but also keeping in mind that BUILD and HOST are nearly
identical:)