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

2009-03-29 Thread Thomas Dickey
On Sun, 29 Mar 2009, Bob Friesenhahn wrote: On Sun, 29 Mar 2009, Thomas Dickey wrote: On Sun, 29 Mar 2009, Bob Friesenhahn wrote: By sufficiently noisy I mean that the user should be able to see the preprocessor and library search paths and any defines provided via the command line so they

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

2009-03-28 Thread Jim Meyering
chmod ... rather than less-readable lines full of gcc command-line options. From 9f39fa8559a8f87e1199f11f6cee295ac8cf6781 Mon Sep 17 00:00:00 2001 From: Jim Meyering meyer...@redhat.com Date: Sat, 28 Mar 2009 12:48:24 +0100 Subject: [PATCH] build: use automake's --silent-rules option when

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

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

2009-03-28 Thread Russ Allbery
Ralf Corsepius rc040...@freenet.de 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