79713039a2
Newer versions of gcc are getting smart enough to detect the sloppy syntax used for the autoconf tests. It is now generating warnings for unused/undeclared variables. Newer version of gcc even have the -Wunused-but-set-variable option set by default. This isn't a problem except when -Werror is set and they get promoted to an error. In this case the autoconf test will return an incorrect result which will result in a build failure latter on. To handle this I'm tightening up many of the autoconf tests to explicitly mark variables as unused to suppress the gcc warning. Remember, all of the autoconf code can never actually be run we just want to get a clean build error to detect which APIs are available. Never using a variable is absolutely fine for this. Closes #176
21 lines
504 B
Plaintext
21 lines
504 B
Plaintext
dnl #
|
|
dnl # 2.6.35 API change
|
|
dnl # The dentry argument was deamed unused and dropped in 2.6.36.
|
|
dnl #
|
|
AC_DEFUN([ZFS_AC_KERNEL_FSYNC_2ARGS], [
|
|
AC_MSG_CHECKING([whether fops->fsync() wants 2 args])
|
|
ZFS_LINUX_TRY_COMPILE([
|
|
#include <linux/fs.h>
|
|
],[
|
|
int (*fsync) (struct file *, int datasync) = NULL;
|
|
struct file_operations fops __attribute__ ((unused));
|
|
|
|
fops.fsync = fsync;
|
|
],[
|
|
AC_MSG_RESULT(yes)
|
|
AC_DEFINE(HAVE_2ARGS_FSYNC, 1, [fops->fsync() want 2 args])
|
|
],[
|
|
AC_MSG_RESULT(no)
|
|
])
|
|
])
|