I have found myself needing to go through the complicated shell
sequence for the $(RECURSIVE_TARGETS) rule more than once when debugging
the Makefile.am's in a big directory tree (namely TeX Live). Typically
I get a mysterious "*** failed", exit status 1, and there's no easy way
to know which comm
1) In the Extending node of the automake (1.10.2) manual, there's a typo:
now: respected by `automake' to ensure the user always have the last word.
new: respected by `automake' to ensure the user always has the last word.
Also, it might be clearer to make each of the following two sentences
* Jim Meyering wrote on Fri, Apr 10, 2009 at 02:51:08PM CEST:
> > 2009-04-10 Ralf Wildenhues
> >
> > Fix parallel distcheck failure.
> > * maint.mk (ALL_RECURSIVE_TARGETS): Add patch-check,
> > check-AUTHORS, maintainer-distcheck, vc-dist, taint-distcheck,
> > my-distcheck, alpha
Ralf Wildenhues wrote:
> * Jim Meyering wrote on Fri, Apr 10, 2009 at 02:07:53PM CEST:
>> On a quad-core system, building "make -j7 distcheck"
>> fails consistently like this: (note the parallel builds of rmdir.o)
>>
>> CC nohup.o
>> CC readlink.o
>> CC rm.o
>> CC rmdir.o
>>
Hi Jim,
thanks for the report.
* Jim Meyering wrote on Fri, Apr 10, 2009 at 02:07:53PM CEST:
> On a quad-core system, building "make -j7 distcheck"
> fails consistently like this: (note the parallel builds of rmdir.o)
>
> CC nohup.o
> CC readlink.o
> CC rm.o
> CC rmdir.o
Jim Meyering wrote:
> On a quad-core system, building "make -j7 distcheck"
> fails consistently like this: (note the parallel builds of rmdir.o)
Oh! I left out an important detail.
This is using automake built from up-to-the-minute "next".
On a quad-core system, building "make -j7 distcheck"
fails consistently like this: (note the parallel builds of rmdir.o)
CC nohup.o
CC readlink.o
CC rm.o
CC rmdir.o
make[3]: Entering directory `/c/coreutils/src'
CC readlink.o
CC stat.o
AR libver.a
