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

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Japin Li <japinli(at)hotmail(dot)com>
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:04:40
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-hackers

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 \

> 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

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


In response to


Browse pgsql-hackers by date

  From Date Subject
Next Message Tristan Partin 2024-03-22 17:05:20 Re: psql not responding to SIGINT upon db reconnection
Previous Message David G. Johnston 2024-03-22 16:55:24 Re: documentation structure