Re: additional GCC warning flags - Mailing list pgsql-patches

From Tom Lane
Subject Re: additional GCC warning flags
Date
Msg-id 17853.1098211020@sss.pgh.pa.us
Whole thread Raw
In response to Re: additional GCC warning flags  (Alvaro Herrera <alvherre@dcc.uchile.cl>)
List pgsql-patches
Alvaro Herrera <alvherre@dcc.uchile.cl> writes:
> There's a better solution: use an approach similar to that used in the
> Linux kernel, which echoes only the object name that's currently being
> compiled.

If I'm reading this correctly, it requires replacing every default build
rule with our own hacked-up version.  That's definitely not a recipe for
maintainability, portability, or playing nice with local
customizations... even if I thought the goal was a good idea, which I do
not particularly.  If I'm looking at make output it's generally because
I need to fix a problem; not knowing exactly what's being executed
is not going to improve my life.

            regards, tom lane

pgsql-patches by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: additional GCC warning flags
Next
From: Reini Urban
Date:
Subject: Re: pg_regress --temp-keep