Hi Jim.
On 08/04/2012 06:30 PM, Jim Meyering wrote:
>
> ACK. Thanks!
>
Thanks for the quick reply. Patch pushed.
Regards,
Stefano
Stefano Lattarini wrote:
> On 08/03/2012 10:14 AM, Stefano Lattarini wrote:
>> On 08/02/2012 07:49 PM, Eric Blake wrote:
>>> On 08/02/2012 11:00 AM, Eric Blake wrote:
On 08/02/2012 10:53 AM, Stefano Lattarini wrote:
> * modules/gnumakefile [Makefile.am]: The makefiles generated by
> Au
On 08/03/2012 10:14 AM, Stefano Lattarini wrote:
> On 08/02/2012 07:49 PM, Eric Blake wrote:
>> On 08/02/2012 11:00 AM, Eric Blake wrote:
>>> On 08/02/2012 10:53 AM, Stefano Lattarini wrote:
* modules/gnumakefile [Makefile.am]: The makefiles generated by
Automake-NG always contain a defin
On 08/02/2012 07:49 PM, Eric Blake wrote:
> On 08/02/2012 11:00 AM, Eric Blake wrote:
>> On 08/02/2012 10:53 AM, Stefano Lattarini wrote:
>>> * modules/gnumakefile [Makefile.am]: The makefiles generated by
>>> Automake-NG always contain a definition of VPATH, even in non-VPATH
>>> builds (its value
On 08/02/2012 11:00 AM, Eric Blake wrote:
> On 08/02/2012 10:53 AM, Stefano Lattarini wrote:
>> * modules/gnumakefile [Makefile.am]: The makefiles generated by
>> Automake-NG always contain a definition of VPATH, even in non-VPATH
>> builds (its value being simply '.' in that case). So, in the
>>
On 08/02/2012 10:53 AM, Stefano Lattarini wrote:
> * modules/gnumakefile [Makefile.am]: The makefiles generated by
> Automake-NG always contain a definition of VPATH, even in non-VPATH
> builds (its value being simply '.' in that case). So, in the
> 'clean-GNUmakefile' rule, to determine whether r
* modules/gnumakefile [Makefile.am]: The makefiles generated by
Automake-NG always contain a definition of VPATH, even in non-VPATH
builds (its value being simply '.' in that case). So, in the
'clean-GNUmakefile' rule, to determine whether running under a
VPATH setup, compare '$(srcdir)' to '.' ra