On Wed, Jun 22, 2022 at 1:11 AM Paul Eggert <egg...@cs.ucla.edu> wrote: > Don't you also need to remove conftest.obj? Or is it conftest.$ac_objext > and require _AC_COMPILER_OBJEXT? Or the latter may be a bridge too far.
Hi Paul, I assumed we don't need to remove conftest.obj because it's not produced by most compilers when the "-o foo" option is used, although I suppose it can't hurt to remove it as well. It also seems we can't use $ac_objext here because this macro AC_COMPILER_EXEEXT must be run before the macro AC_COMPILER_OBJEXT which defines $ac_objext, so I think we must simply hardcode conftest.o.
