Re: AC_PROG_CC_C_O doesn't work with VC++

[Eli Zaretskii]

> Date: Wed, 26 Oct 2005 08:17:52 +0200
> From: Stepan Kasal <address@hidden>
> Cc: address@hidden, address@hidden
> 
> the problem is this: ./configure runs
>       $CC -c -o conftst2.$ac_objext conftest.c
> and then checks whether the compiler created conftst2.$ac_objext or
> conftest$ac_objext
> 
> If it were "conftest2.$ac_objext" instead, and someone run
>       bash ./configure
> in a DJGPP environment, the check might not work.

It _will_ work, even on 8+3 filesystems.  What DOS does, in each one
of its file-oriented system calls, is ``normalize'' the file name
before doing whatever it was asked with the file.  As part of that
``normalization'', file names that exceed 8+3 limits are truncated to
8+3 form.  So the compiler would create, e.g., conftest.xyz instead of
conftest2.xyzt, and the test for whether conftest2.xyzt exists will
succeed because it will happily find conftest.xyz, due to that
``normalization'' I mentioned above.

Does this explain the issue?

> But do people run ./configure as part of a native build in DJGPP?

Yes.  There's a very good port of Bash to DJGPP, and it is quite
capable of running complex configure scripts.