bug#7884: Yacc and FreeBSD make in VPATH builds

2011-01-28 Thread Stefano Lattarini
Hello automakers. JFTR: I've found a prior report of this same issue in the automake mailing list archives, and I think it could be useful to link it here, for completeness: Regards, Stefano

bug#7884: [PATCH] yacc: fix VPATH builds with FreeBSD make (was: Re: bug#7884: Yacc and FreeBSD make in VPATH builds)

2011-01-28 Thread Stefano Lattarini
On Thursday 27 January 2011, Ralf Wildenhues wrote: > Does 'make -n' create files (for any target)? > No, and I've updated the `yaccdry.test' testcase to also check for this (see attached amended patch). > How do you ensure in your patch that 'make distdir' does not create files? > Well, it does,

bug#7884: Yacc and FreeBSD make in VPATH builds

2011-01-28 Thread Stefano Lattarini
On Thursday 27 January 2011, Ralf Wildenhues wrote: > * Stefano Lattarini wrote on Thu, Jan 27, 2011 at 11:54:50AM CET: > > On Tuesday 25 January 2011, Ralf Wildenhues wrote: > > > * Stefano Lattarini wrote on Tue, Jan 25, 2011 at 08:52:56PM CET: > > > > Hmm... maybe a variation of this might be a

bug#7884: Yacc and FreeBSD make in VPATH builds

2011-01-28 Thread Ralf Wildenhues
* Stefano Lattarini wrote on Thu, Jan 27, 2011 at 08:26:42PM CET: > On Thursday 27 January 2011, Ralf Wildenhues wrote: > > I must admit that I still don't like this a lot. BSD is free software, > > we shouldn't have to put ugly workarounds in place for it, and this > > workaround does have some u

bug#7884: [PATCH] yacc: fix VPATH builds with FreeBSD make (was: Re: bug#7884: Yacc and FreeBSD make in VPATH builds)

2011-01-28 Thread Stefano Lattarini
On Thursday 27 January 2011, Stefano Lattarini wrote: > Also, I'm halfway through an automake patch on the lines I've sketched, > and I can say that it seems remarkably easy at this point ... > In fact it has been even easier than I thought, after the discovery that the same 'Automake::Variable::de

bug#7884: Yacc and FreeBSD make in VPATH builds

2011-01-27 Thread Ralf Wildenhues
* Stefano Lattarini wrote on Thu, Jan 27, 2011 at 11:54:50AM CET: > On Tuesday 25 January 2011, Ralf Wildenhues wrote: > > * Stefano Lattarini wrote on Tue, Jan 25, 2011 at 08:52:56PM CET: > > > Hmm... maybe a variation of this might be a good solution after all, at > > > least for FreeBSD make: th

bug#7884: Yacc and FreeBSD make in VPATH builds

2011-01-27 Thread Stefano Lattarini
On Tuesday 25 January 2011, Ralf Wildenhues wrote: > * Stefano Lattarini wrote on Tue, Jan 25, 2011 at 08:52:56PM CET: > > On Saturday 22 January 2011, Ralf Wildenhues wrote: > > > > > > > - Tell the developer to add proper AC_CONFIG_LINKS to configure in > > > >order to support VPATH builds

bug#7884: Yacc and FreeBSD make in VPATH builds

2011-01-25 Thread Ralf Wildenhues
* Stefano Lattarini wrote on Tue, Jan 25, 2011 at 08:52:56PM CET: > On Saturday 22 January 2011, Ralf Wildenhues wrote: > > > > > - Tell the developer to add proper AC_CONFIG_LINKS to configure in > > >order to support VPATH builds with FreeBSD make (yuck^2, since > > >that means keeping

bug#7884: Yacc and FreeBSD make in VPATH builds

2011-01-25 Thread Stefano Lattarini
Hello automakers. A small update on this ... On Saturday 22 January 2011, Ralf Wildenhues wrote: > * Stefano Lattarini wrote on Fri, Jan 21, 2011 at 10:28:24PM CET: > > - Always create yacc-derived and distributed .c and .h files in > >$(srcdir), and explicitly instruct make to alwsys look f

bug#7884: Yacc and FreeBSD make in VPATH builds

2011-01-22 Thread Ralf Wildenhues
* Stefano Lattarini wrote on Fri, Jan 21, 2011 at 10:28:24PM CET: > - Always create yacc-derived and distributed .c and .h files in >$(srcdir), and explicitly instruct make to alwsys look fr them >there at first -- similarly to what is done for info files >(yuck) Yes, this is ugly, bu

bug#7884: Yacc and FreeBSD make in VPATH builds

2011-01-21 Thread Stefano Lattarini
Hello automakers. What I'm going to illustrate here is a long-standing bug in automake; but since I don't see it described in the manual, nor reported in the GNATS database, making it explicitly registered here in Debbugs won't hurt IMHO. -*-*- Here is a description of the bug. 1) The package