Re: Cleaner build output when not much has changed - Mailing list pgsql-hackers

From Alvaro Herrera
Subject Re: Cleaner build output when not much has changed
Date
Msg-id 20140311001239.GO4759@eldon.alvh.no-ip.org
Whole thread Raw
In response to Re: Cleaner build output when not much has changed  (Gurjeet Singh <gurjeet@singh.im>)
Responses Re: Cleaner build output when not much has changed  (Gurjeet Singh <gurjeet@singh.im>)
List pgsql-hackers
Gurjeet Singh wrote:
> On Tue, Nov 26, 2013 at 12:37 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> 
> > Gurjeet Singh <gurjeet@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.

-- 
Álvaro Herrera                http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services



pgsql-hackers by date:

Previous
From: Andrew Dunstan
Date:
Subject: Re: jsonb and nested hstore
Next
From: Bruce Momjian
Date:
Subject: Re: pg_upgrade on high number tables database issues