Re: Problem with cl and autoconf

[Patrick Pelissier]

> >     * lib/autoconf/general.m4 (_AC_PREPROC_IFELSE, _AC_COMPILE_IFELSE,
> >     _AC_LINK_IFELSE): Redirect stdin to /dev/null, in an attempt to
> >     avoid thinking that Allegro Common Lisp's "cl" command is a C++
> >     compiler.
> 
> IIRC, "cl" is the Microsoft C compiler, and so to avoid conflict with
> Allegro Common Lisp's "cl" command, we could just invoke it as
> "CL.EXE" instead.  That is, unless Microsoft port their compiler to a
> non-Windows platform.

 Yes. But even if the problem comes with cl, it may come from another program.

 Sincerely,
  Patrick Pelissier