From: | Andres Freund <andres(at)anarazel(dot)de> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
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:05:27 |
Message-ID: | 20171010170527.npay3qljwbfunymt@alap3.anarazel.de |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
On 2017-10-10 11:01:15 -0400, 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.
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.
> The preferred method if you want to use -Werror is to include it in
> COPT, as mentioned near the bottom of
I think a ./configure --use-werror or something would make this less
painful.
Greetings,
Andres Freund
From | Date | Subject | |
---|---|---|---|
Next Message | John R Pierce | 2017-10-10 17:14:10 | Re: please quote POSTGRESQL |
Previous Message | Tom Lane | 2017-10-10 16:26:28 | Re: ./configure error: Cannot find a working 64-bit integer type |