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

[Kevin P. Fleming]

Kevin Ryde wrote:

> 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.

I just ran into nearly the same problem with an existing package 
(mrouted), whose configure script contains an added macro that does this 
same check. It failed for me building on i686-pc-linux-gnu for 
i386-linux-uclibc. Removing the check from the configure script worked 
find; everything builds and works as expected.