mirror of
git://git.sv.gnu.org/autoconf
synced 2025-04-18 15:30:24 +08:00
* doc/autoconf.texi (Limitations of Usual Tools): Describe
problems with mkdir -p -m.
This commit is contained in:
parent
b98231106c
commit
43a3be8e55
@ -1,3 +1,8 @@
|
||||
2006-10-09 Paul Eggert <eggert@cs.ucla.edu>
|
||||
|
||||
* doc/autoconf.texi (Limitations of Usual Tools): Describe
|
||||
problems with mkdir -p -m.
|
||||
|
||||
2006-10-06 Paul Eggert <eggert@cs.ucla.edu>
|
||||
|
||||
* lib/autoconf/c.m4 (_AC_PROG_PREPROC_WORKS_IFELSE): Remove
|
||||
|
@ -13476,6 +13476,13 @@ No @command{mkdir} option is portable to older systems. Instead of
|
||||
@code{AS_MKDIR_P(@var{file-name})} (@pxref{Programming in M4sh})
|
||||
or @code{AC_PROG_MKDIR_P} (@pxref{Particular Programs}).
|
||||
|
||||
Combining the @option{-m} and @option{-p} options, as in @samp{mkdir -m
|
||||
go-w -p @var{dir}}, often leads to trouble. Free@acronym{BSD}
|
||||
@command{mkdir} incorrectly attempts to change the permissions of
|
||||
@var{dir} even if it already exists. @acronym{HP-UX} 11.23 and
|
||||
@acronym{IRIX} 6.5 @command{mkdir} often assign the wrong permissions to
|
||||
any newly-created parents of @var{dir}.
|
||||
|
||||
Posix does not clearly specify whether @samp{mkdir -p foo}
|
||||
should succeed when @file{foo} is a symbolic link to an already-existing
|
||||
directory. The @acronym{GNU} Core Utilities 5.1.0 @command{mkdir}
|
||||
|
Loading…
x
Reference in New Issue
Block a user