Re: canadian vs build==host configury

[Mohan Embar <gnustuff at thisiscool dot com>]

Hi Adam,

>My inclination is to figure out some way to choose $GCJ and $GCJH
>without relying on $with_cross_host.

This may be a worthy goal, and I understand the top-level configury
contains an admonition that this behavior shouldn't be relied on,
but doing an:

find . -name 'configure.ac' | xargs grep with_cross_host

...shows me a number of cases where this is being relied on.
I can't imagine this being yanked anytime soon without someone
screaming (but then again, what do I know....).

In particular, take a look at boehm-gc's configure.ac. What are
the implications of with_cross_host not being defined when it
really should be?

For me, the path of least resistance seems to be to throw in the towel
and simply set build, host and target explicitly (cf. cfgxgcc.sh, which
I got from Ranjit's original scripts):

BUILD=`$GCC_SRC_DIR/config.guess`
HOST=$BUILD
TARGET=$MINGW32_TARGET_NAME

Or else, it might be possible in the top-level configure script to test
if host="" and target!=`$GCC_SRC_DIR/config.guess` and then set host
to `$GCC_SRC_DIR/config.guess`. This would be legitimizing with_cross_host,
though, which seems to not be what the top-level folks want.

If we really wanted to insist on our right to not set the host explicitly
for cross builds and after verifying that this doesn't break the configury
of other subsystems, we could also check for target!=`$GCC_SRC_DIR/config.guess`
and with_cross_host="" in libjava configure.ac and if this is true, set
with_cross_host to `$GCC_SRC_DIR/config.guess`.

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.

-- Mohan
http://www.thisiscool.com/
http://www.animalsong.org/