Alexandre Duret-Lutz <firstname.lastname@example.org>
This program is free software; you can
redistribute it and/or modify it under the terms of the GNU General Public License
as published by the Free Software Foundation. As a special exception, the respective
Autoconf Macro's copyright owner gives unlimited permission to copy, distribute and modify
the configure scripts that are the output of Autoconf when processing the Macro. You
need not follow the terms of the
GNU General Public License when using or distributing such scripts
cryp.to ac-archive's C Support (released)
Check whether mkdir() is mkdir or _mkdir, and whether it takes one
or two arguments.
This macro can define HAVE_MKDIR, HAVE__MKDIR, and
MKDIR_TAKES_ONE_ARG, which are expected to be used as follows:
# if MKDIR_TAKES_ONE_ARG
/* MinGW32 */
# define mkdir(a, b) mkdir(a)
# if HAVE__MKDIR
/* plain Windows 32 */
# define mkdir(a, b) _mkdir(a)
# error "Don't know how to create a directory on this system."
AC_CACHE_CHECK([whether mkdir takes one argument],
# include <unistd.h>
], [mkdir (".");],
if test x"$ac_cv_mkdir_takes_one_arg" = xyes; then
[Define if mkdir takes only one argument.])
dnl I have not implemented the following suggestion because I don't have
dnl access to such a broken environment to test the macro. So I'm just
dnl appending the comments here in case you have, and want to fix
dnl AC_FUNC_MKDIR that way.
dnl |Thomas E. Dickey (email@example.com) said:
dnl | it doesn't cover the problem areas (compilers that mistreat mkdir
dnl | may prototype it in dir.h and dirent.h, for instance).
dnl | Would it be sufficient to check for these headers and #include
dnl | them in the AC_TRY_COMPILE block? (and is AC_HEADER_DIRENT
dnl | suitable for this?)
dnl | I think that might be a good starting point (with the set of recommended
dnl | ifdef's and includes for AC_HEADER_DIRENT, of course).