Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1da1LG-0008Er-LI for pgsql-hackers@arkaria.postgresql.org; Tue, 25 Jul 2017 15:01:46 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1da1LG-0001F9-1r for pgsql-hackers@arkaria.postgresql.org; Tue, 25 Jul 2017 15:01:46 +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 1da1Ji-0006Rp-Ip for pgsql-hackers@postgresql.org; Tue, 25 Jul 2017 15:00:10 +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 1da1Jg-0007r6-3B for pgsql-hackers@postgresql.org; Tue, 25 Jul 2017 15:00:09 +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 v6PF04L7006806; Tue, 25 Jul 2017 11:00:04 -0400 From: Tom Lane To: Robert Haas cc: Ashutosh Sharma , 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> <32468.1500498091@sss.pgh.pa.us> Comments: In-reply-to Robert Haas message dated "Tue, 25 Jul 2017 10:23:37 -0400" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <6804.1500994804.1@sss.pgh.pa.us> Date: Tue, 25 Jul 2017 11:00:04 -0400 Message-ID: <6805.1500994804@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 Robert Haas writes: > Perl also has a mechanism for flags added to Configure to be passed > along when building loadable modules; if it didn't, not just plperl > but every Perl module written in C would have this issue if any such > flags where used. > ... > While I'm not sure of the details, I suspect that we need to use one > of those methods to get the CCFLAGS used to build perl, and include > those when SPI.o, Util.o, and plperl.o in src/pl/plperl. Or at least > the -D switches from those CCFLAGS. Hm, I had the idea that we were already asking ExtUtils::Embed for that, but now I see we only inquire about LDFLAGS not CCFLAGS. Yes, this sounds like a promising avenue to pursue. It would be useful to see the results of perl -MExtUtils::Embed -e ccopts on one of the affected installations, and compare that to the problematic field(s). 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