Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1dXw6I-0000oi-4J for pgsql-hackers@arkaria.postgresql.org; Wed, 19 Jul 2017 21:01:42 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1dXw6H-0004w5-BI for pgsql-hackers@arkaria.postgresql.org; Wed, 19 Jul 2017 21:01:41 +0000 Received: from makus.postgresql.org ([2001:4800:1501:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1dXw6G-0004vv-L8 for pgsql-hackers@postgresql.org; Wed, 19 Jul 2017 21:01:40 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1dXw6E-00009a-1y for pgsql-hackers@postgresql.org; Wed, 19 Jul 2017 21:01:39 +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 v6JL1VJZ032469; Wed, 19 Jul 2017 17:01:31 -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: <32467.1500498091.1@sss.pgh.pa.us> Date: Wed, 19 Jul 2017 17:01:31 -0400 Message-ID: <32468.1500498091@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: > 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 I am really suspicious that this means your libperl was built in an unsafe fashion, that is, by injecting configuration choices as random -D switches in the build process rather than making sure the choices were recorded in perl's config.h. As an example, looking at the perl 5.24.1 headers on a Fedora box, it looks to me like PERL_SAWAMPERSAND could only get defined if PERL_COPY_ON_WRITE were not defined, and the only way that that can happen is if PERL_NO_COW is defined, and there are no references to the latter anyplace except in this particular #if defined test in perl.h. Where did your perl installation come from, anyway? Are you sure the .h files match up with the executables? regards, tom lane -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers