RE: GNATS needs some work (autoconf/59)

[Tim Van Holder]

> It's not called TARGET. It's called HOST. TARGET is only meaningful for
> compilers and other tools working together to create executables _for_ a
> particular platform.
OK - my bad.

> I'd like to advise you that it would be fair not to support non-UNIX path
> separators on the build system. Autoconf doesn't pretend to support such
> systems.
Then what's the point of supporting DJGPP, OS/2 or Mingw32 (which autoconf
DOES pretend to do)? DJGPP can pretend to be unixy when it comes to pathseps,
but ONLY inside bash (granted, that's where it will matter most, but using ':'
because bash can handle it would break if used inside perl/m4/whatever).

> On the other hand, support for non-UNIX path separators on the host would
> be a feature that very few people need. It falls outside the area of
> "generic" macros that Autoconf contains.
I suppose so. My main point was that there were 2 different issues related
to path separators (build & _HOST_), which the PR didn't seem to take into
account.

> [suggested test snipped]
I suppose this would be a better way to do it (or rather, the Demaillator
Edition of this test :-) ).
I'll try this out on DJGPP and Cygwin bashes and whip up a patch if it
works. OK to add this to the startup code, or would you prefer to have it
AC_REQUIRE/AC_EXPAND_ONCE'd by those macros using a pathsep (such as
AC_CHECK_PROG/AC_PATH_PROG)?