James K. Lowden wrote:
It does make you wish for which(1) or "command -v" for Windows, doesn't
it?
I have which(1), but it doesn't help here ...
I think your plan is reasonable.
The alternative would be to push on configure.guess and assume the
path separator for any form of Windows is a semicolon. I'm not sure
that's more correct, though.
This won't always work. MinGW uses a colon for the path separator, and
MKS provides the option to do so.
(wouldn't any Unix-like system always have /bin/sh?)
Well, yes, because a system without /bin/sh isn't very Unix-like.
But some Windows Unix-like systems (e.g., MKS) have everything in
a different directory. Some environments (e.g., MinGW) do some
machinations to make it appear that the files are in /bin, but others
(again, MKS) get around the most common instance of '/bin/sh' by
searching PATH for the shell.
Sure makes things difficult ...
Jeff Conrad
