Re: [PATCH 0/2] AC_CONFIG_MACRO_DIRS: implementation and documentation

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"

[PATCH] warn: new special syntax warning, hack for aclocal (was: Re: [PATCH 0/2] AC_CONFIG_MACRO_DIRS: implementation and documentation)

Reference: On 11/02/2012 07: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 autom

Re: [PATCH 0/2] AC_CONFIG_MACRO_DIRS: implementation and documentation

On 11/02/2012 06:34 PM, Stefano Lattarini wrote: > On 11/02/2012 02:36 PM, Nick Bowler wrote: >> On 2012-11-02 10:46 +0100, Stefano Lattarini wrote: >>> On 10/23/2012 12:59 AM, Nick Bowler wrote: 4) I get a bunch of new warnings from aclocal, of the form: configure.ac:42: warnin

Re: [PATCH 0/2] AC_CONFIG_MACRO_DIRS: implementation and documentation

On 11/02/2012 02:36 PM, Nick Bowler wrote: > On 2012-11-02 10:46 +0100, Stefano Lattarini wrote: >> On 10/23/2012 12:59 AM, Nick Bowler wrote: >>> 4) I get a bunch of new warnings from aclocal, of the form: >>> >>> configure.ac:42: warning: DX_EXPORTED_SH is m4_require'd but not >>> m4_defun'

Re: [PATCH 0/2] AC_CONFIG_MACRO_DIRS: implementation and documentation

On 2012-11-02 10:46 +0100, Stefano Lattarini wrote: > On 10/23/2012 12:59 AM, Nick Bowler wrote: > > 4) I get a bunch of new warnings from aclocal, of the form: > > > > configure.ac:42: warning: DX_EXPORTED_SH is m4_require'd but not > > m4_defun'd > > > >The invocation comes from an AC

Re: [PATCH 0/2] AC_CONFIG_MACRO_DIRS: implementation and documentation

[+cc: automake-patches, bug-libtool] [re-sending because delivery to automake and autoconf lists failed] References: On 11/01/2012 07:05 PM, Nick B