Only use gcc -Wunused-but-set-variable when available
authorBrian Behlendorf <behlendorf1@llnl.gov>
Fri, 11 Jan 2013 00:09:31 +0000 (16:09 -0800)
committerBrian Behlendorf <behlendorf1@llnl.gov>
Fri, 11 Jan 2013 00:09:39 +0000 (16:09 -0800)
commite191b54ecfbd2af619d5cb4b3a0f298305c2145a
treebf9df5d5985e44a3cb722f9af77632c36ebce15a
parent9566fb1a7b360c44e66475f933ebde106d9a0f0d
Only use gcc -Wunused-but-set-variable when available

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
20 files changed:
config/kernel-bdev-block-device-operations.m4
config/kernel-bdev-logical-size.m4
config/kernel-bdev-physical-size.m4
config/kernel-blk-end-request.m4
config/kernel-blk-fetch-request.m4
config/kernel-blk-queue-discard.m4
config/kernel-blk-queue-flush.m4
config/kernel-blk-queue-io-opt.m4
config/kernel-blk-queue-max-hw-sectors.m4
config/kernel-blk-queue-max-segments.m4
config/kernel-blk-queue-nonrot.m4
config/kernel-blk-queue-physical-block-size.m4
config/kernel-blk-requeue-request.m4
config/kernel-blk-rq-bytes.m4
config/kernel-blk-rq-pos.m4
config/kernel-blk-rq-sectors.m4
config/kernel-elevator-change.m4
config/kernel-get-disk-ro.m4
config/kernel-rq-for-each_segment.m4
config/kernel-rq-is_sync.m4