On 12/20/2011 01:35 PM, Nick Bowler wrote: > On 2011-12-20 13:22 -0700, Eric Blake wrote: >> Furthermore, 'all' is a special syntactic sugar for displaying all other >> warning categories, but is not a warning category itself. m4_warn can >> only be used with the following warning categories (at least, as of >> 2.61, which is what you are targeting as your minimum version): cross, >> obsolete, syntax > > This is not what the autoconf 2.68 manual says. Quoting §8.3.2 > Diagnostic messages from M4sugar: > > — Macro: m4_warn (category, message) > > Report message as a warning (or as an error if requested by the > user) if warnings of the category are turned on. If the message is > emitted, it is prefixed with the current location, and followed by > a call trace of all macros defined via AC_DEFUN used to get to the > current expansion. You are encouraged to use standard categories, > which currently include: > > ‘all’ > messages that don't fall into one of the following categories. > Use of an empty category is equivalent. > ‘cross’ > related to cross compilation issues. Thanks for pointing out that bug. Would anyone care to take a first cut at fixing this bug? I'm not sure whether it is better to fix the documentation to match existing practice, or to alter the autoconf perl script to support 'all'/'' as a catch-all category. I'm actually kind of leaning towards a doc-only fix; gcc already served as a good example that any uncategorized warning is that much harder to turn off; it's simple enough to add new categories, but impossible to handle warnings with no category if you have fine-grained categories for all other warnings. -- Eric Blake eblake@xxxxxxxxxx +1-919-301-3266 Libvirt virtualization library http://libvirt.org
Attachment:
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Autoconf mailing list Autoconf@xxxxxxx https://lists.gnu.org/mailman/listinfo/autoconf
