[PATCH] build: use automake's --silent-rules option when possible

2009-03-28 Thread Jim Meyering
I like automake's upcoming --silent-rules option enough that I'm making it the default (when possible) for coreutils. Since I bootstrap using automake from its "next" branch, it's enabled for me. And that translates to enhanced Makefile.in files in the tarballs I generate. The net result is that

Re: [PATCH] build: use automake's --silent-rules option when possible

2009-03-28 Thread Bob Friesenhahn
On Sat, 28 Mar 2009, Jim Meyering wrote: I like automake's upcoming --silent-rules option enough that I'm making it the default (when possible) for coreutils. Since I bootstrap using automake from its "next" branch, it's enabled for me. And that translates to enhanced Makefile.in files in the t

Re: [PATCH] build: use automake's --silent-rules option when possible

2009-03-28 Thread Ralf Wildenhues
Hi Bob, Jim, * Bob Friesenhahn wrote on Sat, Mar 28, 2009 at 04:40:16PM CET: > On Sat, 28 Mar 2009, Jim Meyering wrote: > >> I like automake's upcoming --silent-rules option enough >> that I'm making it the default (when possible) for coreutils. [...] >> CC id.o > > What happens when things go wr

Re: [PATCH] build: use automake's --silent-rules option when possible

2009-03-28 Thread Jan Engelhardt
On Saturday 2009-03-28 16:44, Ralf Wildenhues wrote: >Hi Bob, Jim, > >* Bob Friesenhahn wrote on Sat, Mar 28, 2009 at 04:40:16PM CET: >> On Sat, 28 Mar 2009, Jim Meyering wrote: >> >>> I like automake's upcoming --silent-rules option enough >>> that I'm making it the default (when possible) for co

Re: Doesn't work: blah_PROGRAMS = $(EXTRA_PROGRAMS)

2009-03-28 Thread Ralf Wildenhues
* Daniel Richard G. wrote on Fri, Mar 27, 2009 at 08:54:10AM CET: > > > > Looks like automake is as confused as you are. For now, here's a > > simple workaround, using a helper variable that is not special to > > automake: > > Oh, a workaround's not a problem; the bug is very narrow. In my case,

Re: [PATCH] build: use automake's --silent-rules option when possible

2009-03-28 Thread Alberto Luaces
El Sábado 28 Marzo 2009ES 17:14:10 Jan Engelhardt escribió: > On Saturday 2009-03-28 16:44, Ralf Wildenhues wrote: > >Hi Bob, Jim, > > > >* Bob Friesenhahn wrote on Sat, Mar 28, 2009 at 04:40:16PM CET: > >> On Sat, 28 Mar 2009, Jim Meyering wrote: > >>> I like automake's upcoming --silent-rules opt

Re: [PATCH] build: use automake's --silent-rules option when possible

2009-03-28 Thread Ralf Corsepius
Jim Meyering wrote: I like automake's upcoming --silent-rules option enough that I'm making it the default (when possible) for coreutils. Well, if you think such a step to be helpful, I disagree. Since I bootstrap using automake from its "next" branch, it's enabled for me. And that translates

Re: [PATCH] build: use automake's --silent-rules option when possible

2009-03-28 Thread Russ Allbery
Ralf Corsepius writes: > Jim Meyering wrote: >> Since I bootstrap using automake from its "next" branch, it's >> enabled for me. And that translates to enhanced Makefile.in >> files in the tarballs I generate. The net result is that when >> you run "make" (using distributed Makefile.in files),

Re: [PATCH] build: use automake's --silent-rules option when possible

2009-03-28 Thread Jim Meyering
Ralf Corsepius wrote: > Jim Meyering wrote: >> I like automake's upcoming --silent-rules option enough >> that I'm making it the default (when possible) for coreutils. > Well, if you think such a step to be helpful, I disagree. Then you can build with "make V=1". >> Since I bootstrap using autom