https://gcc.gnu.org/bugzilla/show_bug.cgi?id=53431
--- Comment #18 from Jonathan Wakely <redi at gcc dot gnu.org> --- You can't control what warnings users enable, but that's no reason not to use -Wall -Wno-unused yourself when building cryptopp. Not polluting you command line seems like a weak excuse given the pollution in the code to support compilers from last millennium (which I know you're getting rid of) and the pollution that loads of compiler-specific pragmas cause. The -Wno-xxx options exist, today, and they work, and even if this bug is fixed it isn't going to be fixed in GCC 4.x or 5.x so the pragmas won't be a complete solution for many years until noone uses today's compilers. Or you could just change the code causing the warnings.
