Re: check for microsoft compiler cl

[Warren Young]

Paul Eggert wrote:
> I assume so, but you may have to consult a Cygwin mailing list.

No, _don't_ bother the Cygwin mailing lists about Visual C++ problems. 
_Way_ inappropriate forum; they'll tell you to use gcc, which auto* will 
use without any problems.

Johannes, if you're just changing the CC variable and expecting it to 
work, that's why you're having problems.  The configure script probably 
assumes that foo.c gets compiled to foo.o and linked to foo.  What cl 
will do is make foo.obj and link that to foo.exe.  Due to the Cygwin 
work, there's probably a way to tell auto* what the platform filename 
extensions are, but this is not a Cygwin problem per se, so don't bother 
them about it.  Just find out what extensions they added to the 
traditional POSIXy core of auto*, and use them.

The other likely problem is a CFLAGS problem.  If it's only trying to 
pass '-g -O2' to cl, cl will deal with that, but if you've got some gcc- 
or POSIX-cc-specific flags in there, cl will probably barf.  The only 
other POSIX cc flag I'm aware of that cl will tolerate is -c.  It won't 
do the right thing with -o at all, for example.

If your problem isn't one of the above things, post the config.log 
section that shows what the configure script tried in order to make a 
test binary.  You can probably figure it out from the errors yourself, 
actually.