On Mon, Mar 10, 2014 at 8:12 PM, Alvaro Herrera <alvhe...@2ndquadrant.com>wrote:
> Gurjeet Singh wrote: > > On Tue, Nov 26, 2013 at 12:37 PM, Tom Lane <t...@sss.pgh.pa.us> wrote: > > > > > Gurjeet Singh <gurj...@singh.im> writes: > > > > I was looking for ways to reduce the noise in Postgres make output, > > > > specifically, I wanted to eliminate the "Nothing to be done for > `all' " > > > > messages, since they don't add much value, and just ad to the > clutter. > > > > > > Why don't you just use "make -s" if you don't want to see that? > > > The example output you show is not much less verbose than before. > > > > I have a shell function that now adds --no-print-directory to my make > > command. This patch combined with that switch makes the output really > clean > > (at least from my perspective). Since the use of a command-line switch > can > > be easily left to personal choice, I am not proposing to add that or its > > makefile-equivalent. But modifying the makefiles to suppress noise is not > > that everyone can be expected to do, and do it right. > > FWIW you can add a src/Makefile.custom file with this: > > all: > @true > > and it will get rid of most noise. > As I noted in the first email in this chain, this causes a warning: GNUmakefile:14: warning: overriding commands for target `all' /home/gurjeet/dev/POSTGRES/src/Makefile.custom:2: warning: ignoring old commands for target `all' I have since settled for `make -s`. On slow builds it keeps me guessing for a long time, without any indication of progress, but I've learned to live with that. Best regards, -- Gurjeet Singh http://gurjeet.singh.im/ EDB www.EnterpriseDB.com <http://www.enterprisedb.com>
