> > 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). As part of my DJGPP patches (still being refined), I made this a variable (ac_test_f), which defaults to '-f'. Site files can then override this (so systems like DOS or NT can simply put ac_test_f='-x' in their config.site and get the behaviour they want).
- 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