pgsql: Only define NO_THREAD_SAFE_LOCALE for MSVC plperl when required

From: Andrew Dunstan <andrew(at)dunslane(dot)net>
To: pgsql-committers(at)lists(dot)postgresql(dot)org
Subject: pgsql: Only define NO_THREAD_SAFE_LOCALE for MSVC plperl when required
Date: 2024-09-14 13:21:59
Message-ID: E1spSit-0014xc-8O@gemulon.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Only define NO_THREAD_SAFE_LOCALE for MSVC plperl when required

Latest versions of Strawberry Perl define USE_THREAD_SAFE_LOCALE, and we
therefore get a handshake error when building against such instances.
The solution is to perform a test to see if USE_THREAD_SAFE_LOCALE is
defined and only define NO_THREAD_SAFE_LOCALE if it isn't.

Backpatch the meson.build fix back to release 16 and apply the same
logic to Mkvcbuild.pm in releases 12 through 16.

Original report of the issue from Muralikrishna Bandaru.

Branch
------
master

Details
-------
https://git.postgresql.org/pg/commitdiff/bc46104fc9aa5254f98250cf2756552f92095ae9

Modified Files
--------------
meson.build | 5 ++++-
1 file changed, 4 insertions(+), 1 deletion(-)

Browse pgsql-committers by date

  From Date Subject
Next Message Bruce Momjian 2024-09-14 13:27:46 pgsql: doc PG 17 relnotes: move EXPLAIN items to their own section
Previous Message Bruce Momjian 2024-09-13 22:22:21 pgsql: doc PG 17 relnotes: move partition access method item