Re: canadian vs build==host configury

[Adam Megacz <megacz at cs dot berkeley dot edu>]

Mohan Embar <gnustuff@thisiscool.com> writes:
> All of this seems like more trouble than it's worth, though. I'd be on
> board with you with your "try to execute the built compiler" trick if it
> weren't for other subsystems' reliance on with_cross_host.

Empirically, I can confirm that none of those other subsystems break
when with_cross_host="".  I can't speak to exactly what they use it
for, but they all cope properly with the case where it is missing.

I think the decision comes down to choosing one of:

  1. Add more code to handle $with_cross_host=""

  2. Don't rely on $with_cross_host

  3. Always bail out with an error when --target is set but --build is
     not, and declare this configuration to be illegal.

I'm okay with any of these, but I'm not really okay with the current
situation where libgcj relies on $with_cross_host to a degree which
other subsystems don't.

The suggestions for how to accomplish #1 without implicitly doing #2
sound reasonable, but I personally do not understand the ramifications
of those changes well enough to feel comfortable making them myself.
If we could convince the top-level people to make sure that
(canonical) $build, $target, and $host are always set to something
non-empty, that would be ideal.

Is #3 acceptable?

  - a

-- 
PGP/GPG: 5C9F F366 C9CF 2145 E770  B1B8 EFB1 462D A146 C380