On 2022-01-31 10:43:31 -0500, Andrew Dunstan wrote:
> We should fix that, maybe along these lines?
WFM.
On 10/4/21 18:02, Andres Freund wrote:
> Hi,
>
> On 2021-10-04 14:38:16 -0700, Andres Freund wrote:
>> 2) For some reason src/tools/install.pl doesn't install plperl[u].control,
>>plperl[u]--1.0.sql - But apparently the buildfarm doesn't have that issue,
>>because drongo successfully ran
Hi,
On 2022-01-30 15:14:32 -0800, Noah Misch wrote:
> Last I looked (~2017), EDB distributed an MSVC-built Perl as the designated
> Perl to use with https://www.postgresql.org/download/windows/ plperl.
Ah, interesting. I didn't find a perl binary in the archive offered, and I
didn't immediately f
On Sun, Jan 30, 2022 at 02:16:59PM -0800, Andres Freund wrote:
> Specifically where USE_THREAD_SAFE_LOCALE is defined for msvc. Which explains
> why the same perl build ends up with different definitions for
> PerlInterpreter, depending on headers getting compiled with gcc or
> msvc.
>
> Seems pre
Hi,
On 2022-01-30 12:56:16 -0800, Andres Freund wrote:
> The gcc version has a Ilc_numeric_mutex_depth that the msvc version
> doesn't. The relevant part of intrpvar.h:
>
> PERLVAR(I, in_utf8_turkic_locale, bool)
> #if defined(USE_ITHREADS) && ! defined(USE_THREAD_SAFE_LOCALE)
> PERLVARI(I, lc_nu
Hi,
On 2021-10-04 14:38:16 -0700, Andres Freund wrote:
> 3) When building against strawberry perl 5.32.1.1 I see errors when loading
>plperl
The error is:
loadable library and perl binaries are mismatched (got handshake key
12800080, needed 12900080)
A bunch of research led
Hi,
On 2021-10-04 14:38:16 -0700, Andres Freund wrote:
> 3) When building against strawberry perl 5.32.1.1 I see errors when loading
>plperl
>
> 4) When building against strawberry perl 5.30.3.1 I see a crash during
>execution of very simple statements [1]
>
> 5) Finally when building agai
Hi,
On 2021-10-04 14:38:16 -0700, Andres Freund wrote:
> 2) For some reason src/tools/install.pl doesn't install plperl[u].control,
>plperl[u]--1.0.sql - But apparently the buildfarm doesn't have that issue,
>because drongo successfully ran the plperl tests?
Oh, figured that one out: Inst
