mirror/autoconf
2
0
Fork 0
mirror of git://git.sv.gnu.org/autoconf synced 2025-01-18 10:45:15 +08:00
Code Issues Packages Projects Releases Wiki Activity

typos

Browse Source
This commit is contained in:
Stepan Kasal 2006-03-20 14:46:12 +00:00
parent 4342ba1ca8
commit 2ea44d31c2
3 changed files with 13 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
ChangeLog
View File

@ -1,3 +1,11 @@
2006-03-20 Stepan Kasal <kasal@ucw.cz>
* 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 <kasal@ucw.cz>
* lib/autoconf/programs.m4 (AC_PATH_TOOL, AC_CHECK_TOOL, AC_CHECK_TOOLS):

4
doc/autoconf.texi
View File

@ -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

6
lib/autoconf/lang.m4
View File

@ -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.