Re: Cross-compiling guide

[Roland McGrath]

That all looks about right according to my memory.  
(I've never used "stow", but modulo that.)

I usually use a shorter target alias like `i386-gnu', since i386-gnu-gcc is
nicer to type than i386-unknown-gnu0.3-gcc.  If you are just building for
yourself, then it's worthwhile to use the appropriate machine for what you
actually care to run on, i.e. i686-gnu is what I use.  I think that makes
gcc default to optimal code generation for the right chip family (as
opposed to needing -mtune=foo or something), and it builds the optimal
assembly code flavors in glibc.  Configuring glibc for less than i486 may
be significantly suboptimal.

Note that if you want to do things strictly in dependency order (or
parallelize the steps you can), building mig really only requires the
cross-gcc and mach headers.  (Building a cross-mig doesn't need the
cross-binutils, but of course you need to have installed them before you
build the cross-gcc anyway.)

The circularity with building libgcc has always been a pain that I have
muddled through each time, pretty much done what your recipe says but
always by hand with too many fumbles.  I would really like to see the true
dependencies figured out and a gcc makefile patch to provide targets we can
use to do the necessary steps cleanly and without ignoring errors.


Thanks,
Roland