From: | Bruce Momjian <bruce(at)momjian(dot)us> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Martijn van Oosterhout <kleptog(at)svana(dot)org>, Andrew Dunstan <andrew(at)dunslane(dot)net>, pgsql-hackers(at)postgresql(dot)org, Kris Jurka <books(at)ejurka(dot)com> |
Subject: | Re: src/tools/pginclude considered harmful (was Re: |
Date: | 2006-07-14 23:13:19 |
Message-ID: | 200607142313.k6ENDJw21762@momjian.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-patches |
Tom Lane wrote:
> Bruce Momjian <bruce(at)momjian(dot)us> writes:
> > Tom Lane wrote:
> >> BTW, one of the remaining holes in pgrminclude is that it compiles with
> >> -fsyntax-only, which apparently causes it to fail to detect some errors
> >> of significance --- I assume that's how it managed to foul up lmgr.c,
> >> inet_net_ntop.c, etc.
>
> > But I do run a full compile and regression before commit, so that should
> > have caught it even if pgrminclude didn't.
>
> Doesn't catch warnings (unless you add -Werror during the build, which
> will have problems with the remaining expected warnings...)
/tools/pgtest always greps out the warnings and displays them at the end
of the regression tests.
--
Bruce Momjian bruce(at)momjian(dot)us
EnterpriseDB http://www.enterprisedb.com
+ If your life is a hard drive, Christ can be your backup. +
From | Date | Subject | |
---|---|---|---|
Next Message | Neil Conway | 2006-07-14 23:19:04 | Re: src/tools/pginclude considered harmful (was Re: |
Previous Message | Tom Lane | 2006-07-14 23:06:20 | Re: src/tools/pginclude considered harmful (was Re: [PATCHES] |
From | Date | Subject | |
---|---|---|---|
Next Message | Neil Conway | 2006-07-14 23:19:04 | Re: src/tools/pginclude considered harmful (was Re: |
Previous Message | Tom Lane | 2006-07-14 23:06:20 | Re: src/tools/pginclude considered harmful (was Re: [PATCHES] |