Re: multiple outputs rule

2007-01-27 Thread Ralf Wildenhues
* Bruno Haible wrote on Fri, Dec 15, 2006 at 01:14:43PM CET: > [ a good patch that I think there's no need to wait longer for approval ] > > Oops, I meant to remove only data.lock here. The suggested patch is this: Thanks again, I've applied this to branch-1-10 and HEAD. Cheers, Ralf 2007-01-27

Re: multiple outputs rule

2006-12-15 Thread Bruno Haible
Ralf Wildenhues wrote: > > ## This code is being executed by the first process. > > rm -f data.stamp; \ > > $(MAKE) $(AM_MAKEFLAGS) data.stamp; \ > > result=$$?; rm -rf data.lock data.stamp; exit $$result; \ > > Do you really want to remove t

Re: multiple outputs rule

2006-12-14 Thread Ralf Wildenhues
Hello Bruno, Thank you for the bug report. * Bruno Haible wrote on Thu, Dec 14, 2006 at 03:04:20PM CET: > 2) When the first branch of the "if mkdir ..." is executed, the data.lock > directory is never removed. It should be removed after the recursive $(MAKE) > invocation, preserving the return co

multiple outputs rule

2006-12-14 Thread Bruno Haible
Hi, The automake-1.10 documentation contains this sample rule: data.c data.h data.w data.x: data.stamp ## Recover from the removal of $@ @if test -f $@; then :; else \ trap 'rm -rf data.lock data.stamp 1 2 13 15; \ ## mkdir is a portable test-and-set