On Sun, Nov 1, 2009 at 1:49 AM, Ralf Wildenhues <Ralf.Wildenhues@xxxxxx> wrote: > names='gcc gcc[0-9_-]* cc c89 c99 cgcc clang llvm-gcc sdcc tcc > xlc xlc_r bgxlc icc ecc pgcc pathcc ccc nvcc cl bcc bcc32' > ... dir in $PATH /usr/ucb,ext in '' .exe ... > cand=$dir/$name$ext > if test -f "$cand"; then interesting that this looks for "cl.exe" but not for "CL.EXE". I though uppercase would be correct - at least what is installed by default, so we called our wrapper script (for linux+WINE as build, for win32 as host) also uppercase. Was this wrong? Is anyone using cl? Where? On windows, configure (.sh) cannot be run, so what is used? WINE, cygwin, MSYS? Steffen _______________________________________________ Autoconf mailing list Autoconf@xxxxxxx http://lists.gnu.org/mailman/listinfo/autoconf
