[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: MKS sh problem (follow-up)
From: |
Tim Van Holder |
Subject: |
Re: MKS sh problem (follow-up) |
Date: |
Mon, 24 Nov 2003 12:05:23 +0100 |
> Win32 Issue
> -----------
> Configure correctly discovers '.exe' as the executable suffix, but
> doesn't use it when searching for C and C++ compilers, so it fails to
> find cl in either case. Changing every instance of 'cl' to 'cl.exe'
> effects a quick fix, but making use of the executable suffix would be
> more elegant as well as more portable. Setting the variables 'CC' and
> 'CXX' is another interim fix.
Another fix is to set ac_executable_extensions to ".exe"
(or ".exe .cmd .bat" if you like) in your config.site.
That variable was added for this exact purpose - not all Unixy shells
on DOS/Windows return true for 'test -x foo' if only foo.exe exists.
I suppose autoconf could add $EXEEXT to this variable automatically,
but that really gives a chicken-and-egg problem, as in order to determine
the extension the compiler adds, it needs to compile & link a test program,
and for that it needs to find the compiler first, for which it needs the
extension.