On 2017-10-13 14:19:22 -0400, Tom Lane wrote:
> > So it'd probably better to introduce a FORCE_DISABLE_RESTRICT=yes, set
> > at the same place, that's then tested before running the relevant
> > configure check?
>
> +1. I think you don't actually have to skip the configure check,
> and there might be some value in letting it carry on normally
> (so that "restrict" is set properly). We'd just want it to affect
> what pg_restrict gets defined as. Something like
> if test "$ac_cv_c_restrict" = "no" -o "x$FORCE_DISABLE_RESTRICT" = "xyes"; then
> pg_restrict=""
> else
> pg_restrict="$ac_cv_c_restrict"
Yea, that works. Will make it so.
Greetings,
Andres Freund
--
Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-committers