e191b54ecf
Certain versions of gcc generate an 'unrecognized command
line option' error message when -Wunused-but-set-variable
is used unconditionally. This in turn can cause several
of the autoconf tests to misdetect an interface.
Now, the use of -Wunused-but-set-variable in the autoconf
tests was introduced by commit b9c59ec8 to address a gcc
4.6 compatibility problem. So we really only need to pass
this option for version of gcc which are known to support it.
Therefore, the tests have been updated to use the result of
the existing ZFS_AC_CONFIG_ALWAYS_NO_UNUSED_BUT_SET_VARIABLE
which determines if gcc supports this option.
Signed-off-by: Brian Behlendorf <behlendorf1@llnl.gov>
Closes #1004
37 lines
1.1 KiB
Plaintext
37 lines
1.1 KiB
Plaintext
dnl #
|
|
dnl # 2.6.x API change
|
|
dnl #
|
|
AC_DEFUN([ZFS_AC_KERNEL_BDEV_BLOCK_DEVICE_OPERATIONS], [
|
|
AC_MSG_CHECKING([block device operation prototypes])
|
|
tmp_flags="$EXTRA_KCFLAGS"
|
|
EXTRA_KCFLAGS="${NO_UNUSED_BUT_SET_VARIABLE}"
|
|
ZFS_LINUX_TRY_COMPILE([
|
|
#include <linux/blkdev.h>
|
|
],[
|
|
int (*blk_open) (struct block_device *, fmode_t) = NULL;
|
|
int (*blk_release) (struct gendisk *, fmode_t) = NULL;
|
|
int (*blk_ioctl) (struct block_device *, fmode_t,
|
|
unsigned, unsigned long) = NULL;
|
|
int (*blk_compat_ioctl) (struct block_device *, fmode_t,
|
|
unsigned, unsigned long) = NULL;
|
|
struct block_device_operations blk_ops = {
|
|
.open = blk_open,
|
|
.release = blk_release,
|
|
.ioctl = blk_ioctl,
|
|
.compat_ioctl = blk_compat_ioctl,
|
|
};
|
|
|
|
blk_ops.open(NULL, 0);
|
|
blk_ops.release(NULL, 0);
|
|
blk_ops.ioctl(NULL, 0, 0, 0);
|
|
blk_ops.compat_ioctl(NULL, 0, 0, 0);
|
|
],[
|
|
AC_MSG_RESULT(struct block_device)
|
|
AC_DEFINE(HAVE_BDEV_BLOCK_DEVICE_OPERATIONS, 1,
|
|
[struct block_device_operations use bdevs])
|
|
],[
|
|
AC_MSG_RESULT(struct inode)
|
|
])
|
|
EXTRA_KCFLAGS="$tmp_flags"
|
|
])
|