build status for cross builds?

[Paul Koning]

>>>>> "dewar" == dewar  <dewar@gnat.com> writes:

 dewar> I have no idea what Paul is talking about, we do cross-builds
 dewar> all the time on both GCC 2.8.1 and GCC 3. The latter is for
 dewar> the sparc64 VxWorks port that we have in beta testing.

Maybe the problem is that some targets work and some don't.  I'll
ignore the playing around I'm doing with the pdp11 target... :-)

The target I have been talking about is mips.  I expect to be able to
do something like this:

   tar xf <gcc tarball>
   mkdir gccbin; cd gccbin
   ../gcc-<version>/configure --target=mips-xyz
   make all

It seems sensible that this should work.  (It does for various other
packages, e.g., binutils.)  

But the above has *never* worked for me -- it always blows up around
the first references to xgcc, traditionally in configure with "xgcc
cannot create binaries".

Yes, I can ignore the error, cd gcc; make install -- but that sort of
procedure is undocumented and goes against logic and expectations.

If I try what CrossFAQ suggests, and build from a "combined source
tree", then I get farther.  But as I've mentioned before, at least for
mips-netbsd I trip over irreconcilable conflicts among .h files from
various components, so that either libgcc2 or libstdc++ simply refuse
to build.

I don't want to go as far as Joseph Myers suggests and say that this
issue should block checkins.  It's not exactly a new problem.  The
point of my comments is to emphasize that this is a nasty problem that
(at least as one perceives it from the outside) is not getting a whole
lot of attention.

    paul