On 11/02/2012 12:34 PM, Stefano Lattarini wrote: > Well, it turns out that such warnings are coming from the autom4te > invocation, so I see no simple, non-hacky way to avoid them, unless > we add a knob to autom4te itself. > > So, autoconfers: would be OK with you to add a new warning "category" > to autom4te that would suppress *only* this specific warning? > The warning in question being > > AC_FOO is m4_require'd but not m4_defun'd > > that is emitted by the '_m4_require_call' internal macro (defined in > 'lib/m4sugar/m4sugar.m4').
Maybe not a new syntax category, but a way to selectively disable just that warning. I'm thinking of adding a witness macro; something like wrapping the existing [m4_warn([syntax]...)] within _m4_require_call inside an m4_ifdef([_m4_require_no_warning]) probe; then we supply a trivial definition of the _m4_require_no_warning witness macro in its own .m4f file. Then we can modify lib/autom4te.in so that the Autoconf-without-aclocal-m4 language does not use the dedicated file (ergo, the witness is not present and there is no warning issued when encountering required macros); but the Autoconf, Autotest, Automate, M4sh, and M4sugar languages DO use the dedicated file and therefore get the warning. -- Eric Blake ebl...@redhat.com +1-919-301-3266 Libvirt virtualization library http://libvirt.org
signature.asc
Description: OpenPGP digital signature
