bug#13514: unintentional regression with AC_CONFIG_MACRO_DIR in 1.13.1

2013-01-23 Thread Pavel Raiskup
> .. 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

2013-01-23 Thread Pavel Raiskup
>>> [..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#13524: Improving user experience for non-recursive builds

2013-01-23 Thread Stefano Lattarini
On 01/23/2013 03:34 PM, Peter Rosin wrote: > On 2013-01-23 13:45, Stefano Lattarini wrote: >> Hi Peter, thanks for the patch. >> >> Not sure if you are in the mood (or have the time) to engage in a >> discussion about it, but here my review anyway. Even if you are not >> going to work on this patc

bug#13524: Improving user experience for non-recursive builds

2013-01-23 Thread Peter Rosin
On 2013-01-23 13:45, Stefano Lattarini wrote: > Hi Peter, thanks for the patch. > > Not sure if you are in the mood (or have the time) to engage in a > discussion about it, but here my review anyway. Even if you are not > going to work on this patch anymore, a review will still be useful > as a r

bug#13514: unintentional regression with AC_CONFIG_MACRO_DIR in 1.13.1

2013-01-23 Thread Pavel Raiskup
> [..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#13524: Improving user experience for non-recursive builds

2013-01-23 Thread Stefano Lattarini
Hi Peter, thanks for the patch. Not sure if you are in the mood (or have the time) to engage in a discussion about it, but here my review anyway. Even if you are not going to work on this patch anymore, a review will still be useful as a reference to me or other developers in the future. On 01/2

bug#13524: Improving user experience for non-recursive builds

2013-01-23 Thread Stefano Lattarini
Hello Miles, thanks for the feedback. On 01/23/2013 07:54 AM, Miles Bader wrote: > Stefano Lattarini writes: >>> E.g., if I have a directory "foo" that has sources etc, and builds >>> some specific targets, then I can isolate the automake stuff for foo >>> by using an include file "foo/Makefile.a

bug#13435: Please don't kill DJGPP support...

2013-01-23 Thread Stefano Lattarini
Reference: On 01/14/2013 11:29 PM, DJ Delorie wrote: > > Stefano Lattarini wrote: >> >> Well, then it appear we might actually have no problems in keeping DJGPP >> support. If the new code with split info files disabled works as expected, >> re

bug#13514: unintentional regression with AC_CONFIG_MACRO_DIR in 1.13.1

2013-01-23 Thread Stefano Lattarini
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