[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Problem with cl and autoconf
From: |
James Youngman |
Subject: |
Re: Problem with cl and autoconf |
Date: |
Fri, 11 Feb 2005 07:17:55 +0000 |
User-agent: |
Mutt/1.3.28i |
On Thu, Feb 10, 2005 at 04:42:44PM -0800, Paul Eggert wrote:
> * 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.
James.
- Re: Problem with cl and autoconf, Paul Eggert, 2005/02/10
- Re: Problem with cl and autoconf,
James Youngman <=
- Re: Problem with cl and autoconf, Alexandre Duret-Lutz, 2005/02/11
- Re: Problem with cl and autoconf, Paul Eggert, 2005/02/11
- Re: Problem with cl and autoconf, Noah Misch, 2005/02/12
- Re: Problem with cl and autoconf, Paul Eggert, 2005/02/13
- Re: Problem with cl and autoconf, Andreas Buening, 2005/02/13
- Re: Problem with cl and autoconf, Paul Eggert, 2005/02/14
- Re: Problem with cl and autoconf, Alexandre Duret-Lutz, 2005/02/14