diff options
| author | Brian Behlendorf <[email protected]> | 2011-04-19 10:02:21 -0700 |
|---|---|---|
| committer | Brian Behlendorf <[email protected]> | 2011-04-19 10:10:47 -0700 |
| commit | 79713039a2b6e0ed223d141b4a8a8455f282d2f2 (patch) | |
| tree | 0412c6b2e5794ff3d8b7500d5c30959cd7795a41 /config/kernel-fmode-t.m4 | |
| parent | 03514b01109e0a6ef4eee4914ba7442c380fa6b4 (diff) | |
Fix gcc configure warnings
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
Diffstat (limited to 'config/kernel-fmode-t.m4')
| -rw-r--r-- | config/kernel-fmode-t.m4 | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/config/kernel-fmode-t.m4 b/config/kernel-fmode-t.m4 index cf25d8127..4a23c391d 100644 --- a/config/kernel-fmode-t.m4 +++ b/config/kernel-fmode-t.m4 @@ -7,7 +7,7 @@ AC_DEFUN([ZFS_AC_KERNEL_TYPE_FMODE_T], ZFS_LINUX_TRY_COMPILE([ #include <linux/types.h> ],[ - fmode_t *ptr; + fmode_t *ptr __attribute__ ((unused)); ],[ AC_MSG_RESULT([yes]) AC_DEFINE(HAVE_FMODE_T, 1, |