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

[Paolo Bonzini]

Replying to Eric:

> For API consistency, wouldn't it also make sense to introduce macros
> AC_CHECK_HOST_TOOL, AC_CHECK_HOST_TOOLS, and AC_PATH_HOST_TOOLS; and to
> deprecate AC_CHECK_TOOL, AC_CHECK_TOOLS, and AC_PATH_TOOL?

No, because AC_CHECK_TARGET_TOOL is specialized enough that it isn't worth
complicating the name of AC_CHECK_TOOL.  In principle, AC_CHECK_TOOL is
AC_CHECK_HOST_PROG, nothing more :-)

> It seems like this description should be worded just like the description
> for AC_CHECK_TARGET_TOOLS, where you say "If none of the tools can be found
> with a prefix, and if the build and target types are equal, then the first
> one without a prefix is used."

Right.

Replying to Ralf:

> IMO, no, because AFAIS you seem to be mixing up target and host.
>
> In autoconf host != build denotes cross compilation, IMO cross tools
> should be picked up if build != host.

You seem to be confusing the new macros (like AC_CHECK_TARGET_TOOL) with the
change I made to AC_CHECK_TOOL and friends (holler while keeping the old
behavior, if build != host).

Paolo