On Wed, Jan 17, 2001 at 10:13:58AM +0100, Akim Demaille wrote: > >>>>> "Lars" == Lars J Aas <[EMAIL PROTECTED]> writes: > > Lars> A better fix would be to have AC_PATH_PROG (or whichever macro > Lars> it is that searches for the compiler) to also consider implied > Lars> exe- extensions on systems that use them, and add the extension > Lars> to the returned program name. > > The real good fix will be to use test -x IMHO. This ought to work in > this case, right? ...assuming that you don't use it w/o checking that it works. (of course if it happens to not work on a platform where you need a exe-extension, then you've only wasted time). -- Thomas E. Dickey <[EMAIL PROTECTED]> http://dickey.his.com ftp://dickey.his.com
- AC_PROG_CC problems on Windows with MKS Shell Wan-Teh Chang
- Re: AC_PROG_CC problems on Windows with MKS Shell Lars J. Aas
- Re: AC_PROG_CC problems on Windows with MKS Shell Wan-Teh Chang
- Re: AC_PROG_CC problems on Windows with MKS Shell Thomas Dickey
- Re: AC_PROG_CC problems on Windows with MKS Shell Lars J. Aas
- Re: AC_PROG_CC problems on Windows with MKS Shell Akim Demaille
- RE: AC_PROG_CC problems on Windows with MKS Shell Thomas Dickey
- RE: AC_PROG_CC problems on Windows with MKS Shell Tim Van Holder
- Re: AC_PROG_CC problems on Windows with MKS Shell Akim Demaille
- Re: AC_PROG_CC problems on Windows with MKS Shell Lars J. Aas
- Re: AC_PROG_CC problems on Windows with MKS Shell Akim Demaille
- Re: AC_PROG_CC problems on Windows with MKS Shell Lars J. Aas
- Re: AC_PROG_CC problems on Windows with MKS Shell Akim Demaille
- RE: AC_PROG_CC problems on Windows with MKS Shell Tim Van Holder