bug#13514: unintentional regression with AC_CONFIG_MACRO_DIR in 1.13.1

[+cc automake-patches] Reference: Related ticket: On 02/08/2013 01:56 PM, Pavel Raiskup wrote: > Hi Stefano, > Hi Pavel, and thanks for the patches. Your work is really a

bug#13514: unintentional regression with AC_CONFIG_MACRO_DIR in 1.13.1

On Fri, 2013-02-08 at 13:56 +0100, Pavel Raiskup wrote: > Hi Stefano, > > > >> [ ... ] > > > > > > Ping. Are you considering my opinions OK? > > > > > Basically yes; and a patch would obviously be welcome, if you want > > to speed up the fixing of this bug ;-) > > First proposal attached :) (00

bug#13514: unintentional regression with AC_CONFIG_MACRO_DIR in 1.13.1

Hi Stefano, > >> [ ... ] > > > > Ping. Are you considering my opinions OK? > > > Basically yes; and a patch would obviously be welcome, if you want > to speed up the fixing of this bug ;-) First proposal attached :) (0001-*). > > Quickly again (let's say that AC_CONFIG_MACRO_DIR([m4]) is speci

bug#13514: unintentional regression with AC_CONFIG_MACRO_DIR in 1.13.1

On 02/04/2013 11:00 AM, Pavel Raiskup wrote: >> [ ... ] > > Ping. Are you considering my opinions OK? > Basically yes; and a patch would obviously be welcome, if you want to speed up the fixing of this bug ;-) > Quickly again (let's say that AC_CONFIG_MACRO_DIR([m4]) is specified): > a) Warn b

bug#13514: unintentional regression with AC_CONFIG_MACRO_DIR in 1.13.1

> [ ... ] Ping. Are you considering my opinions OK? Quickly again (let's say that AC_CONFIG_MACRO_DIR([m4]) is specified): a) Warn because 'aclocal -I m4' wants to search 'm4' dir which does not exist. Ignoring this completely is imo idea; b) Don't fail in that because it breaks autore

bug#13514: unintentional regression with AC_CONFIG_MACRO_DIR in 1.13.1

> .. because this tool specifies where libtool should put .m4 files ... This is bad statement — autoreconf does not specify this. But its configure.ac does and autoreconf knows better than any tool (imo) how to solve this. Pavel

bug#13514: unintentional regression with AC_CONFIG_MACRO_DIR in 1.13.1

>>> [..skip..] >>> Maybe the current error should be demoted to a warning, to allow us to >>> be more forward-compatible with such possible future scenarios? >> >> I vote for this approach. >> >I'm starting to be convinced myself that it is the best one. > > But then again, mulling over the issue a

bug#13514: unintentional regression with AC_CONFIG_MACRO_DIR in 1.13.1

> [..skip..] > Maybe the current error should be demoted to a warning, to allow us to > be more forward-compatible with such possible future scenarios? I vote for this approach. It was also proposed some time ago (it is transitively hyper-linked from here already): http://lists.gnu.org/archive

bug#13514: unintentional regression with AC_CONFIG_MACRO_DIR in 1.13.1

On 01/23/2013 12:04 PM, Pavel Raiskup wrote: >> [..skip..] >> Maybe the current error should be demoted to a warning, to allow us to >> be more forward-compatible with such possible future scenarios? > > I vote for this approach. > I'm starting to be convinced myself that it is the best one. But

bug#13514: unintentional regression with AC_CONFIG_MACRO_DIR in 1.13.1

Hi Eric, thanks for the report. On 01/21/2013 02:31 PM, Eric Blake wrote: > See https://bugzilla.redhat.com/show_bug.cgi?id=901333 for details; but > the short summary is: > > The xorg-x11-drv-wacom uses AC_CONFIG_MACRO_DIR([m4]) to tell libtool > where to dump m4 macros, but has no m4 macros of

bug#13514: unintentional regression with AC_CONFIG_MACRO_DIR in 1.13.1

See https://bugzilla.redhat.com/show_bug.cgi?id=901333 for details; but the short summary is: The xorg-x11-drv-wacom uses AC_CONFIG_MACRO_DIR([m4]) to tell libtool where to dump m4 macros, but has no m4 macros of its own. Therefore, it does not ship an m4 directory in its git project. When libto