Hello,
On Mon, Oct 24, 2005 at 01:41:27PM -0700, Paul Eggert wrote:
> > Is there any C, Fortran, or F77 compiler which could create other
> > conftst2.* files if it receives -o conftst2.$ac_objext ?
>
> Quite possibly, yes.
OK, so I committed the patch attached below.
> But why not name these files "conftest2.c" etc? [...] We don't need
> to worry about 8.3 file systems any more, on development platforms
> anyway.
I know about 3 different Woe32 environments (though I don't use any):
1) Cygwin
2) MinGW
3) MinGW + MSYS
1) Cygwin doesn't have the 8.3 limitation.
2) MinGW proper doesn't have any POSIX shell, so it cannot run configure.
3) There is an MSYS build of bash. Though MinGW/MSYS is not ready
to run Autoconf, you can use it to unpack a tarball and run ./configure
there.
Is it possible that ./configure will then run in the 8.3 environment?
I don't know and that is why I am not ready to drop the 8.3 support from
generated ./configure.
Have a nice day,
Stepan Kasal
2005-10-25 Stepan Kasal <kasal@xxxxxx>
* lib/autoconf/c.m4 (AC_PROG_CC_C_O): rm -f conftst2.*, not only
conftst2.$ac_objext.
* lib/autoconf/fortran.m4 (_AC_PROG_FC_C_O): Likewise.
Index: lib/autoconf/c.m4
===================================================================
RCS file: /cvsroot/autoconf/autoconf/lib/autoconf/c.m4,v
retrieving revision 1.205
diff -u -r1.205 c.m4
--- lib/autoconf/c.m4 24 Oct 2005 10:56:01 -0000 1.205
+++ lib/autoconf/c.m4 25 Oct 2005 07:43:18 -0000
@@ -577,12 +577,12 @@
AC_CACHE_VAL(ac_cv_prog_cc_${ac_cc}_c_o,
[AC_LANG_CONFTEST([AC_LANG_PROGRAM([])])
ac_clean_files_save=$ac_clean_files
-ac_clean_files="$ac_clean_files conftst2.$ac_objext"
+ac_clean_files="$ac_clean_files conftst2.*"
# Make sure it works both with $CC and with simple cc.
# We do the test twice because some compilers refuse to overwrite an
# existing .o file with -o, though they will create one.
ac_try='$CC -c conftest.$ac_ext -o conftst2.$ac_objext >&AS_MESSAGE_LOG_FD'
-rm -f conftst2.$ac_objext
+rm -f conftst2.*
if AC_TRY_EVAL(ac_try) &&
test -f conftst2.$ac_objext && AC_TRY_EVAL(ac_try);
then
@@ -591,7 +591,7 @@
# Test first that cc exists at all.
if AC_TRY_COMMAND(cc -c conftest.$ac_ext >&AS_MESSAGE_LOG_FD); then
ac_try='cc -c conftest.$ac_ext -o conftst2.$ac_objext >&AS_MESSAGE_LOG_FD'
- rm -f conftst2.$ac_objext
+ rm -f conftst2.*
if AC_TRY_EVAL(ac_try) &&
test -f conftst2.$ac_objext && AC_TRY_EVAL(ac_try);
then
@@ -606,7 +606,7 @@
else
eval ac_cv_prog_cc_${ac_cc}_c_o=no
fi
-rm -f conftest* conftst2.$ac_objext
+rm -f conftest* conftst2.*
ac_clean_files=$ac_clean_files_save
])dnl
if eval "test \"`echo '$ac_cv_prog_cc_'${ac_cc}_c_o`\" = yes"; then
Index: lib/autoconf/fortran.m4
===================================================================
RCS file: /cvsroot/autoconf/autoconf/lib/autoconf/fortran.m4,v
retrieving revision 1.196
diff -u -r1.196 fortran.m4
--- lib/autoconf/fortran.m4 24 Oct 2005 10:56:02 -0000 1.196
+++ lib/autoconf/fortran.m4 25 Oct 2005 07:43:18 -0000
@@ -460,11 +460,11 @@
[ac_cv_prog_[]_AC_LANG_ABBREV[]_c_o],
[AC_LANG_CONFTEST([AC_LANG_PROGRAM([])])
ac_clean_files_save=$ac_clean_files
-ac_clean_files="$ac_clean_files conftst2.$ac_objext"
+ac_clean_files="$ac_clean_files conftst2.*"
# We test twice because some compilers refuse to overwrite an existing
# `.o' file with `-o', although they will create one.
ac_try='$[]_AC_FC[] $[]_AC_LANG_PREFIX[]FLAGS -c conftest.$ac_ext -o conftst2.$ac_objext >&AS_MESSAGE_LOG_FD'
-rm -f conftst2.$ac_objext
+rm -f conftst2.*
if AC_TRY_EVAL(ac_try) &&
test -f conftst2.$ac_objext &&
AC_TRY_EVAL(ac_try); then
@@ -472,7 +472,7 @@
else
ac_cv_prog_[]_AC_LANG_ABBREV[]_c_o=no
fi
-rm -f conftest* conftst2.$ac_objext
+rm -f conftest* conftst2.*
ac_clean_files=$ac_clean_files_save
])
if test $ac_cv_prog_[]_AC_LANG_ABBREV[]_c_o = no; then
_______________________________________________
Autoconf mailing list
Autoconf@xxxxxxx
http://lists.gnu.org/mailman/listinfo/autoconf
