On 6/30/13 11:26 AM, Andres Freund wrote:
> If we would treat that warning as an error unconditionally - and I am
> not sure how easy that is given the way it's emitted - users
> encountering them, which usually will be on less common platforms, will
> have to patch configure.in to make things work for them. Which is a high
> bar.
> Given that many of those warnings will *NOT* completely prohibit them
> from building postgres that might be overreaching.
We could also look into updating Autoconf. Newer versions proceed with
the compiler's result. At that point, you can essentially ignore the
warning.
