AC_PROG_CC problems on Windows with MKS Shell

[Wan-Teh Chang]

I am trying to use autoconf on Windows with the
MKS Toolkit, which consists of a Korn shell and
the usual Unix utilities.

I first had to modify config.guess and config.sub
to recognize the output of the 'uname' command of
MKS.  Currently, config.guess and config.sub seem
to only recognize Cygwin and U/WIN.

Now the fun part.  AC_PROG_CC fails for me for
two reasons:
1. It tries to find the program 'cl' on the PATH.
   However, the MKS shell takes the specified
   pathname literally and does not automatically
   append the .exe suffix.  I found that if I
   manually modify the configure script to use
   'cl.exe', then it works.
2. The PATH variable in MKS uses a semicolon (;)
   as path separator so that pathnames can use
   drive letters (C:, D:, etc.).  However,
   AC_PROG_CC assumes colon (:) is the path
   separator.  Again, if I manually modify the
   configure script to use ; as path separator,
   then it works.

Is there a macro that detects the path separator
character (: or ;) for use in other macros such
as AC_PROG_CC?

Can AC_PROG_CC be modified to look for 'cl.exe'
instead of 'cl' on Windows?  I think that both
Cygwin and U/WIN should be able to handle 'cl.exe'.

Where can I find information about the upcoming
autoconf release, in particular, its support for
Windows?

Thanks,
Wan-Teh