Re: Cannot find a working 64-bit integer type on Illumos

From: Japin Li <japinli(at)hotmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Cannot find a working 64-bit integer type on Illumos
Date: 2024-03-22 17:22:56
Message-ID: ME3P282MB31664F951A5107C0C9AFF486B6312@ME3P282MB3166.AUSP282.PROD.OUTLOOK.COM
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


On Sat, 23 Mar 2024 at 01:04, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Japin Li <japinli(at)hotmail(dot)com> writes:
>> When I try to configure PostgreSQL 16.2 on Illumos using the following command,
>> it complains $subject.
>
>> ./configure --enable-cassert --enable-debug --enable-nls --with-perl \
>> --with-python --without-tcl --without-gssapi --with-openssl \
>> --with-ldap --with-libxml --with-libxslt --without-systemd \
>> --with-readline --enable-thread-safety --enable-dtrace \
>> DTRACEFLAGS=-64 CFLAGS=-Werror
>
>> However, if I remove the `CFLAGS=-Werror`, it works fine.
>> I'm not sure what happened here.
>
> CFLAGS=-Werror breaks a whole lot of configure's tests, not only that
> one. (We even have this documented, see [1].) So you can't inject
> -Werror that way. What I do on my buildfarm animals is the equivalent
> of
>
> export COPT='-Werror'
>
> after configure and before build. I think configure pays no attention
> to COPT, so it'd likely be safe to keep that set all the time, but in
> the buildfarm client it's just as easy to be conservative.
>
> regards, tom lane
>
> [1] https://www.postgresql.org/docs/devel/install-make.html#CONFIGURE-ENVVARS

Thank you very much! I didn't notice this part before.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2024-03-22 17:25:56 Re: Cannot find a working 64-bit integer type on Illumos
Previous Message Tomas Vondra 2024-03-22 17:22:29 Re: pg_upgrade --copy-file-range