Source: corosync
Version: 2.3.5-5
Severity: important
Tags: patch
User: [email protected]
Usertags: hurd
Hello,
Currently corosync FTBFS on GNU/Hurd due to lack of definitions of two constants
PATH_MAX and PIPE_BUF. The attached patch fixes this by defining PATH_MAX to
4096 in configure.ac if not defined in <limits.h> and PIPE_BUF to
_POSIX_PIPE_BUF in configure.ac if not defined in <limits.h>.
Thanks!
Index: corosync-2.3.5/configure.ac
===================================================================
--- corosync-2.3.5.orig/configure.ac
+++ corosync-2.3.5/configure.ac
@@ -441,6 +441,14 @@ if test "x${enable_rdma}" = xyes; then
PACKAGE_FEATURES="$PACKAGE_FEATURES rdma"
WITH_LIST="$WITH_LIST --with rdma"
fi
+ AC_CHECK_DECL([PATH_MAX], [], [], [#include <limits.h>])
+ if test "x${ac_cv_have_decl_PATH_MAX}" = "xno"; then
+ AC_DEFINE_UNQUOTED([PATH_MAX], [4096] , [Define PATH_MAX if not defined])
+ fi
+ AC_CHECK_DECL([PIPE_BUF], [], [], [#include <limits.h>])
+ if test "x${ac_cv_have_decl_PIPE_BUF}" = "xno"; then
+ AC_DEFINE_UNQUOTED([PIPE_BUF], [_POSIX_PIPE_BUF] , [Define PIPE_BUF to _POSIX_PIPE_BUF if not defined])
+ fi
if test "x${enable_monitoring}" = xyes; then
PKG_CHECK_MODULES([statgrab], [libstatgrab])
