Re: !USE_WIDE_UPPER_LOWER compile errors in v10+

From: Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>
To: Noah Misch <noah(at)leadboat(dot)com>
Cc: Peter Geoghegan <pg(at)bowt(dot)ie>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: !USE_WIDE_UPPER_LOWER compile errors in v10+
Date: 2017-09-21 18:44:17
Message-ID: 509cd374-4693-4592-5787-38696814f3e6@2ndquadrant.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 9/21/17 01:29, Noah Misch wrote:
> I checked !USE_WIDE_UPPER_LOWER by configuring v10 as follows:
>
> ./configure -C --prefix=$HOME/sw/nopath/pg10 --enable-debug \
> --enable-cassert --enable-depend --enable-tap-tests --with-libxml \
> --with-gssapi --with-openssl ac_cv_func_towlower=no
>
> The result fails to compile:

Yeah, the placement of the ifdef blocks was pretty bogus. This patch
fixes it.

--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

Attachment Content-Type Size
0001-Fix-build-with-USE_WIDE_UPPER_LOWER.patch text/plain 2.7 KB

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2017-09-21 18:58:09 Re: [COMMITTERS] pgsql: Fix bool/int type confusion
Previous Message Pavel Stehule 2017-09-21 18:30:19 Re: Re: proposal - psql: possibility to specify sort for describe commands, when size is printed