Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1dXtPm-0006y2-0l for pgsql-hackers@arkaria.postgresql.org; Wed, 19 Jul 2017 18:09:38 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1dXtPl-0007vF-Jc for pgsql-hackers@arkaria.postgresql.org; Wed, 19 Jul 2017 18:09:37 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1dXtPk-0007u3-C6 for pgsql-hackers@postgresql.org; Wed, 19 Jul 2017 18:09:36 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1dXtPd-0000n4-4w for pgsql-hackers@postgresql.org; Wed, 19 Jul 2017 18:09:35 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.4/8.14.4) with ESMTP id v6JI9MBK007363; Wed, 19 Jul 2017 14:09:22 -0400 From: Tom Lane To: Ashutosh Sharma cc: Andrew Dunstan , Dave Page , Sandeep Thakkar , "pgsql-hackers@postgresql.org" Subject: Re: pl/perl extension fails on Windows In-reply-to: References: <4569.1499873707@sss.pgh.pa.us> <6063dd4c-cd1e-d9d8-fa0d-3bddb1403c66@2ndQuadrant.com> <184f1fb9-dfa2-ef2d-024b-7933486e018a@2ndQuadrant.com> <16093.1499956602@sss.pgh.pa.us> <7480.1499965218@sss.pgh.pa.us> <30585.1500480763@sss.pgh.pa.us> Comments: In-reply-to Ashutosh Sharma message dated "Wed, 19 Jul 2017 23:14:58 +0530" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <7361.1500487762.1@sss.pgh.pa.us> Content-Transfer-Encoding: quoted-printable Date: Wed, 19 Jul 2017 14:09:22 -0400 Message-ID: <7362.1500487762@sss.pgh.pa.us> List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-hackers Precedence: bulk Sender: pgsql-hackers-owner@postgresql.org Ashutosh Sharma writes: > On Wed, Jul 19, 2017 at 9:42 PM, Tom Lane wrote: >> I imagine the route to a solution is to fix things so that the relevant >> macros are all defined correctly in both cases. But why they aren't >> already is certainly an interesting question. Have you identified just >> which fields are added or missing relative to what libperl thinks? > Here are the list of macros and variables from 'intrpvar.h' file that > are just defined in perl module but not in plperl on Windows, > #ifdef PERL_USES_PL_PIDSTATUS > PERLVAR(I, pidstatus, HV *) /* pid-to-status mappings for waitpid= */ > #endif > #ifdef PERL_SAWAMPERSAND > PERLVAR(I, sawampersand, U8) /* must save all match strings */ > #endif > #ifdef FCRYPT > PERLVARI(I, cryptseen, bool, FALSE) /* has fast crypt() been initiali= zed? */ > #else > /* One byte hole in the interpreter structure. */ > #endif > #ifdef USE_REENTRANT_API > PERLVAR(I, reentrant_buffer, REENTR *) /* here we store the _r buffers */ > #endif > #ifdef PERL_GLOBAL_STRUCT_PRIVATE > PERLVARI(I, my_cxt_keys, const char **, NULL) /* per-module array of > pointers to MY_CXT_KEY constants */ > # endif > #ifdef DEBUG_LEAKING_SCALARS_FORK_DUMP > /* File descriptor to talk to the child which dumps scalars. */ > PERLVARI(I, dumper_fd, int, -1) > #endif > #ifdef DEBUG_LEAKING_SCALARS > PERLVARI(I, sv_serial, U32, 0) /* SV serial number, used in sv.c */ > #endif > #ifdef PERL_TRACE_OPS > PERLVARA(I, op_exec_cnt, OP_max+2, UV) > #endif Huh. So those seem like symbols that ought to be exposed somewhere in Perl's headers. Perhaps we're failing to #include some "perl_config.h" or equivalent file that records these ABI options? regards, tom lane --=20 Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers