From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Jim Nasby <Jim(dot)Nasby(at)BlueTreble(dot)com> |
Cc: | Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Shrink volume of default make output |
Date: | 2017-01-02 21:57:23 |
Message-ID: | 6675.1483394243@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Jim Nasby <Jim(dot)Nasby(at)BlueTreble(dot)com> writes:
> The recent thread about compiler warnings got me thinking about how it's
> essentially impossible to notice warnings with default make output.
> Perhaps everyone just uses make -s by default, though that's a bit
> annoying since you get no output unless something does warn (and then
> you don't know what directory it was in).
> Is it worth looking into this? I'm guessing this may be moot with the
> CMake work, but it's not clear when that'll make it in. In the meantime,
> ISTM http://stackoverflow.com/a/218295 should be an easy change to make
> (though perhaps with a variable that gives you the old behavior).
I'm not really sure which of the kluges in that article you're proposing
we adopt, but none of them look better than "make -s" to me. Also,
none of them would do anything about make's own verbosity such as
"entering/leaving directory" lines.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Joe Conway | 2017-01-02 22:53:31 | Re: Compiler warnings |
Previous Message | Jim Nasby | 2017-01-02 21:37:04 | Shrink volume of default make output |