guile_cv_struct_utimbuf_needs_posix=no,
guile_cv_struct_utimbuf_needs_posix=yes)])
if test "$guile_cv_struct_utimbuf_needs_posix" = yes; then
- AC_DEFINE(UTIMBUF_NEEDS_POSIX)
+ AC_DEFINE([UTIMBUF_NEEDS_POSIX], 1,
+ [Define this if <utime.h> doesn't define struct utimbuf unless
+ _POSIX_SOURCE is defined. See GUILE_STRUCT_UTIMBUF in aclocal.m4.])
fi])
[
AC_CHECK_HEADERS(libc.h unistd.h)
AC_CACHE_CHECK(
- "whether libc.h and unistd.h can be included together",
+ [whether libc.h and unistd.h can be included together],
guile_cv_header_libc_with_unistd,
[
if test "$ac_cv_header_libc_h" = "no"; then
]
)
if test "$guile_cv_header_libc_with_unistd" = yes; then
- AC_DEFINE(LIBC_H_WITH_UNISTD_H)
+ AC_DEFINE(LIBC_H_WITH_UNISTD_H, 1,
+ [Define this if we should include <libc.h> when we've already
+ included <unistd.h>. On some systems, they conflict, and libc.h
+ should be omitted. See GUILE_HEADER_LIBC_WITH_UNISTD in
+ aclocal.m4.])
fi
]
)
which can conflict with char $1(); below. */
#include <assert.h>
/* Override any gcc2 internal prototype to avoid an error. */
-]ifelse(AC_LANG, CPLUSPLUS, [#ifdef __cplusplus
+#ifdef __cplusplus
extern "C"
#endif
-])dnl
-[/* We use char because int might match the return type of a gcc2
+/* We use char because int might match the return type of a gcc2
builtin and then its argument prototype would still apply. */
char $1();
], [