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

[Paul Eggert]

"Paolo Bonzini" <address@hidden> writes:

> It might have worked badly in the cases I explain above, and it
> definitely did not work when a package had to compile tools that run
> on the build system.

Yes, it failed for some important cases.  But it's easier to use than
the more-general case, and it works well in some important special
cases.  I've used it myself, for building applications where the build
process does not need to compile tools that run on the build system (a
not uncommon situation).

It is a confusing area for people like me who don't do cross-builds
much.  There is a tension between supporting just one way to do
cross-builds, that will support an arbitrary cross-build strategy; and
supporting different ways to do cross-builds, some of them easier to
understand and use (but more limited).

I sense that you'd rather support the former, and obviously this
suffices.  Still, it'd be nice to also support the latter, if someone
is willing to get this to work.