Hello, On Thu, Oct 27, 2005 at 12:09:22PM -0700, Paul Eggert wrote: > If memory serves the name change from conftst2.c to conftest2.c means > we don't have to worry about cleaning the files up separately, since > the already-existing "rm -f conftest*" will clean them up. yes, the previous patch had to change ac_clean_files. > [...] we shouldn't clutter Autoconf up with comments about 8+3, [...] OK, deleted that comment, see the attached patch. > While we're on that subject, there may still be reasons to live within > the 14-byte file name length limit of original Unix, [...] Does this limitation affect the Autoconf somehow? A quick grep revealed that the 14 byte limit was the reson for AM_MAKEINFOFLAGS = --no-split in doc/Makefile.am. The there is AC_SYS_LONG_FILE_NAMES, of course. I don't see any need for any change. Stepan
2005-11-01 Stepan Kasal <kasal@xxxxxx> * lib/autoconf/c.m4 (AC_PROG_CC_C_O): Remove the comment about 8+3 filesystems. Index: lib/autoconf/c.m4 =================================================================== RCS file: /cvsroot/autoconf/autoconf/lib/autoconf/c.m4,v retrieving revision 1.207 diff -u -r1.207 c.m4 --- lib/autoconf/c.m4 27 Oct 2005 06:16:04 -0000 1.207 +++ lib/autoconf/c.m4 1 Nov 2005 07:18:46 -0000 @@ -579,9 +579,6 @@ # 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. -# (On an 8+3 filesystem, conftest2.* is not distinguishable from conftest.*, -# thus the test always passes; but if the ./configure scripts are ever run -# on good old DOS, it has to be with DJGPP, thus with gcc.) ac_try='$CC -c conftest.$ac_ext -o conftest2.$ac_objext >&AS_MESSAGE_LOG_FD' rm -f conftest2.* if AC_TRY_EVAL(ac_try) &&
_______________________________________________ Autoconf mailing list Autoconf@xxxxxxx http://lists.gnu.org/mailman/listinfo/autoconf
