Re: Warn on naked cross-tool names, add macros to detect target tools

[Kevin Ryde]

Bonzini <address@hidden> writes:
>
> +    if test "$build" != "$host"; then
> +      AC_MSG_WARN([In the future, Autoconf will not detect cross-tools
> +whose name does not start with the host triplet.

I think this is unnecessarily restrictive.  One case it would hurt a
bit is compiling for instance on build=i386-pc-linux-gnu for
host=i686-pc-linux-gnu.  This is a cross compile in the sense that the
tuples are not the same and the host code won't run on the build
system, but it can almost certainly use the build system native tools.

If there's a worry that an unprefixed tool might not be right, then
I'd suggest trying to make a test to see if it can do what it's meant
to do, rather than demanding a particular name.  That'd have the
advantage of detecting various kinds of tool problems nice and early.