cross compiler questions

["Joseph H. Buehler" <jhpb at sarto dot gaithersburg dot md dot us>]

I am building an rs6000-ibm-aix3.2.5 cross compiler so I can
distribute a big software build across multiple machines, and have a
few questions regarding setup.

- Before building the cross-compiler, I put the native C library
includes and libs in /usr/local/rs6000-ibm-aix3.2.5/include and
/usr/local/rs6000-ibm-aix3.2.5/lib, via symlinks to NFS mounts.  Can I
remove all those symlinks once the build is done, or does gcc still
need them?

I build the cross-compiler on several different NFS servers, one for
each architecture that I am using.  The machines that need to run them
then mount from the appropriate server.  Some of these machines are
actually rs6000-ibm-aix3.2.5 machines that have no native compiler.
So I build the native compiler and NFS export it from a server, and
mount it where it is needed.  Except that this does not work, because
the header files are not on the machines that don't have a compiler.

- Is there a way to get a file layout similar to that of a
cross-compiler, when doing a native build, so I don't need the header
files and libraries native to the machine?

- I compared the output of some of the cross-builds.  The directories
/usr/local/rs6000-ibm-aix3.2.5/ and /usr/local/lib/gcc-lib/whatever (I
forget the path for the egcs build output) seem to be identical on the
cross-build machines, except for the compiler executables (obviously)
and some .a files.  It seems as though the build process could be
streamlined quite a bit by getting the .a and include files from
another machine that has already done a cross-build, and just making
the necessary executables.  The rs6000-ibm-aix3.2.5 cross-build takes
about 4 hours on a couple of the machines I am using, and a lot of it
seems to result from building varieties of a couple of the .a files.
So maybe a build option to not do the fixinclude stuff or compile any
cross-libraries, and just assume that they are already there, in the
right place?

- Are there any instructions on how to do builds, and the various
options that are available?  I have been assuming that the
documentation is not up to date, hopefully I am wrong.

Joe Buehler