From: Stepan Kasal Date: Mon, 20 Mar 2006 14:46:12 +0000 (+0000) Subject: typos X-Git-Tag: AUTOCONF-2.59c~131 X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=2ea44d31c2dfe50e692e2dff87b216005404324c;p=thirdparty%2Fautoconf.git typos --- diff --git a/ChangeLog b/ChangeLog index 67b3e1c80..6b9d30351 100644 --- a/ChangeLog +++ b/ChangeLog @@ -1,3 +1,11 @@ +2006-03-20 Stepan Kasal + + * doc/autoconf.texi (Default Includes): Fix typo + s/AC_HEADERS_STDC/AC_HEADER_STDC/ + (Limitations of Usual Tools): s/unwriteable/unwritable/ + * lib/autoconf/lang.m4 (_AC_COMPILER_EXEEXT_DEFAULT, _AC_COMPILER_EXEEXT): + Fix typos in the comments. + 2006-03-17 Stepan Kasal * lib/autoconf/programs.m4 (AC_PATH_TOOL, AC_CHECK_TOOL, AC_CHECK_TOOLS): diff --git a/doc/autoconf.texi b/doc/autoconf.texi index 127bf7963..4f5306d00 100644 --- a/doc/autoconf.texi +++ b/doc/autoconf.texi @@ -3361,7 +3361,7 @@ Expand to @var{include-directives} if defined, otherwise to: If the default includes are used, then check for the presence of these headers and their compatibility, i.e., you don't need to run -@code{AC_HEADERS_STDC}, nor check for @file{stdlib.h} etc. +@code{AC_HEADER_STDC}, nor check for @file{stdlib.h} etc. These headers are checked for in the same order as they are included. For instance, on some systems @file{string.h} and @file{strings.h} both @@ -12150,7 +12150,7 @@ compiler name. @prindex @command{chmod} Avoid usages like @samp{chmod -w file}; use @samp{chmod a-w file} instead, for two reasons. First, plain @samp{-w} does not necessarily -make the file unwriteable, since it does not affect mode bits that +make the file unwritable, since it does not affect mode bits that correspond to bits in the file mode creation mask. Second, Posix says that the @samp{-w} might be interpreted as an implementation-specific option, not as a mode; Posix suggests diff --git a/lib/autoconf/lang.m4 b/lib/autoconf/lang.m4 index 76110f1c0..6d38b67a8 100644 --- a/lib/autoconf/lang.m4 +++ b/lib/autoconf/lang.m4 @@ -455,8 +455,8 @@ AC_DEFUN([AC_OBJEXT], []) # --------------------------- # Check for the extension used for the default name for executables. # -# We do this in order to find out what is the extension we must for -# compiling executables (see _AC_COMPILER_EXEEXT's comments). +# We do this in order to find out what is the extension we must add for +# creating executables (see _AC_COMPILER_EXEEXT's comments). # # Beware of `expr' that may return `0' or `'. Since this macro is # the first one in touch with the compiler, it should also check that @@ -591,7 +591,7 @@ AC_MSG_RESULT([$ac_cv_exeext]) # # Note that some compilers (cross or not), strictly obey to `-o foo' while # the host requires `foo.exe', so we should not depend upon `-o' to -# test EXEEXT. But then, be sure no to destroy user files. +# test EXEEXT. But then, be sure not to destroy user files. # # Must be run before _AC_COMPILER_OBJEXT because _AC_COMPILER_EXEEXT_DEFAULT # checks whether the compiler works.