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

From: Дилян Палаузов <dpa-postgres(at)aegee(dot)org>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: PostgreSQL Bugs <pgsql-bugs(at)postgresql(dot)org>
Subject: Re: ./configure error: Cannot find a working 64-bit integer type
Date: 2017-10-10 15:19:54
Message-ID: 740c3046-6632-f2ec-8b42-0ace33760066@aegee.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Hello Tom,

if the aim is one day to be able to run with -Werror, as far as the problems are within PG, then this snippet needs to be fixed one day, and today is a good opportunity for this particular piece.

Regards
  Дилян

On 10/10/17 17:01, Tom Lane wrote:
> =?UTF-8?B?0JTQuNC70Y/QvSDQn9Cw0LvQsNGD0LfQvtCy?= <dpa-postgres(at)aegee(dot)org> writes:
>> unless the patch below is applied ./configure prints:
> 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.
>
> The preferred method if you want to use -Werror is to include it in
> COPT, as mentioned near the bottom of
>
> https://www.postgresql.org/docs/current/static/install-procedure.html
>
> regards, tom lane

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Aleksander Alekseev 2017-10-10 15:22:51 Re: 10.0: Logical replication doesn't execute BEFORE UPDATE OF <columns> trigger
Previous Message Tom Lane 2017-10-10 15:01:15 Re: ./configure error: Cannot find a working 64-bit integer type