On 4 Jul 2000, Alexandre Oliva wrote:
> Can you point to any configure.in code for which this makes any
> difference? Remember, we're just not setting build_alias=$host_alias
> any more. We won't be assuming cross-compilation just because they
> happen to be different, in this case.
There is none, only what the user passes makes a diff.
> The point was to not assume cross-compilation just because --host was
> specified. Now this is accomplished as follows:
That is fine with me. In fact that is much less of a "revert"
than I thought you were making.
> The warning, as it is now, is not perfect, but what you suggest just
> doesn't match the current implementation.
Agreed, I was under the impression you wanted to still support
the old --host sets --build semantics. I guess we can just
chalk this one up to mis-communication.
> > The old semantics would set $build to i386-pc-linux with the following:
>
> > ./configure --host=i386-pc-linux
>
> I understand. But a guessed build probably would be pretty close to
> the specified --host, unless you're actually cross-compiling, in which
> case having --build guessed is an actual improvement. I don't see
> much point in retaining backward compatibility in this case, do you?
Nope, this is much cleaner than what I thought we had agreed to.
It simply means that people who are used to setting the --build
using --host are going to have to change to --build.
It also sort of "tosses out" whatever is passed as the
argument to --host if it is not used to detect a cross compiler.
Mo DeJong
Red Hat Inc
