Re: ./configure error: Cannot find a working 64-bit integer type

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Andres Freund <andres(at)anarazel(dot)de>
Cc: Дилян Палаузов <dpa-postgres(at)aegee(dot)org>, PostgreSQL Bugs <pgsql-bugs(at)postgresql(dot)org>
Subject: Re: ./configure error: Cannot find a working 64-bit integer type
Date: 2017-10-10 17:18:39
Message-ID: 3325.1507655919@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Andres Freund <andres(at)anarazel(dot)de> writes:
> On 2017-10-10 11:01:15 -0400, Tom Lane wrote:
>> You can't run configure with -Werror; there are too many things it does
>> that aren't clean according to bleeding-edge compilers. This particular
>> issue is only the tip of the iceberg, and most of the problems are not
>> ours but Autoconf's, so we can't fix them.

> Right. It's to the point I wonder if we shouldn't error out in configure
> and/or filter it out if Werror is specified. If the latter we could
> still leave it enabled in the persisted cflags.

Hm, filtering it out and then putting it back at the end would be a
pretty transparent fix. I don't feel like investing work in that,
but if you do ...

regards, tom lane

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2017-10-10 18:07:36 Re: BUG #14830: Missed NOTIFications, PostgreSQL 9.1.24
Previous Message John R Pierce 2017-10-10 17:14:10 Re: please quote POSTGRESQL