public inbox for [email protected]
help / color / mirror / Atom feedFrom: Tom Lane <[email protected]>
To: Japin Li <[email protected]>
Cc: PostgreSQL Hackers <[email protected]>
Subject: Re: Cannot find a working 64-bit integer type on Illumos
Date: Fri, 22 Mar 2024 13:04:40 -0400
Message-ID: <[email protected]> (raw)
In-Reply-To: <ME3P282MB3166F9D1F71F787929C0C7E7B6312@ME3P282MB3166.AUSP282.PROD.OUTLOOK.COM>
References: <ME3P282MB3166F9D1F71F787929C0C7E7B6312@ME3P282MB3166.AUSP282.PROD.OUTLOOK.COM>
Japin Li <[email protected]> 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
view thread (3+ messages) latest in thread
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: [email protected]
Cc: [email protected], [email protected], [email protected]
Subject: Re: Cannot find a working 64-bit integer type on Illumos
In-Reply-To: <[email protected]>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox