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

[Ralf Corsepius]

On Tue, 2004-03-16 at 13:08, Eric Sunshine wrote:
> On Tue, 16 Mar 2004 06:23:22 -0500, Bonzini wrote:
> > For target tools, it makes no sense to me to have naked names, so I am
> > already looking for prefixed names only.  Ok to apply?
> > * lib/autoconf/programs.m4 (AC_PATH_TOOL, AC_CHECK_TOOL,
> > AC_CHECK_TOOLS): Warn if a cross-tool is found without
> > a prefix.
> > (AC_PATH_TARGET_TOOL, AC_CHECK_TARGET_TOOL,
> > AC_CHECK_TARGET_TOOLS): New macros.
> > * doc/autoconf.texi (Generic Programs): Document
> > (AC_PATH_TARGET_TOOL, AC_CHECK_TARGET_TOOL,
> > AC_CHECK_TARGET_TOOLS, and warn for future changes
> > in the behavior of AC_PATH_TOOL, AC_CHECK_TOOL and
> > AC_CHECK_TOOLS.
> 
> 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?
IMO, this doesn't make sense. Instead, AC_CHECK_TOOL[S] should be
changed to not trying the "non-prefixed" tools for $host != $build

However, this would break backward compatibility, therefore introducing
a new macro to replace AC_CHECK_TOOL[S] in longer terms might be
appropriate.

Ralf