Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1mbAIa-0003hc-Op for pgsql-hackers@arkaria.postgresql.org; Thu, 14 Oct 2021 23:38:08 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1mbAIZ-0000BD-Kx for pgsql-hackers@arkaria.postgresql.org; Thu, 14 Oct 2021 23:38:07 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1mbAIZ-0000Av-C7 for pgsql-hackers@lists.postgresql.org; Thu, 14 Oct 2021 23:38:07 +0000 Received: from out1-smtp.messagingengine.com ([66.111.4.25]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1mbAIW-0008NY-W7 for pgsql-hackers@postgresql.org; Thu, 14 Oct 2021 23:38:06 +0000 Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.nyi.internal (Postfix) with ESMTP id 13F945C0181; Thu, 14 Oct 2021 19:38:04 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute4.internal (MEProxy); Thu, 14 Oct 2021 19:38:04 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=anarazel.de; h= date:from:to:cc:subject:message-id:references:mime-version :content-type:in-reply-to; s=fm2; bh=dk0EpawuTPiEo3lUfVIGSLXSXun NefGmWbvySgNFuXQ=; b=tqzlDvkM4xfIvolRRNojZEWXXHWwf6w4rhry28+hr3k tH3Jck1MVOEwmif8E/7FjiDEpYh1/ybMqfE1cWmQZcgdBUhg5IQ+jCidOjazvtby uS3tT/dHsdzLzkkAEETE4e88E4DsVUMs6vKZYczK3pc5fPxMva4G+d2fVg+WA2Xq QMjN6WDT85wzA++GrkD4EBvCYXHvJunIU8G6n/mCjW1P2bVEIWsF7BnbonkYuVdi WmrCTi0+zGFhuhEAAAEDg3+DYbQgQmuJT/k2UtYtsBULdj7jThALYegFCLWVpTt9 EoZltDQz58FDGQpGyidJqY/CqUYHplnaHy9Rpq5h17Q== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm1; bh=dk0Epa wuTPiEo3lUfVIGSLXSXunNefGmWbvySgNFuXQ=; b=ZPcBcwaMqHzKM+hRKd/hgv 21P67D6ua9HHIHuQgCG22Gr0fNhFBf9AQf53gPNeARBoPmkUwu1onhzb9slO7hHO lNqiSJmhpTnZJTBx+jOxuclRQxsJHLN7Fs1SJSaQpbljpf+mQVcnrl8dX8dlxRre sO+lqCn38teAVhMLSUY1VY9otmlINqPFAGBhoFGPB7dhcPL/Q+JjLeDYmLSw27cm AsO3KzXdsHnfgLMqMBQw+jqJeoW8R7kVujWvqIFEyzCruxksD7EF1hzMnNBNX0kx +9eTme+vGQYEAcHEZMd4lAe9clVlJiLtT9Rt+/xdYYQAfLdWKcr7VmXhFTG6g65A == X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvtddrvddufedgvdduucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhepfffhvffukfhfgggtuggjsehttdertddttddvnecuhfhrohhmpeetnhgurhgv shcuhfhrvghunhguuceorghnughrvghssegrnhgrrhgriigvlhdruggvqeenucggtffrrg htthgvrhhnpedukefhkeelueegveetheelffffjeegleeuudelfeefuedtleffueejfffh ueffudenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfhhrohhmpe grnhgurhgvshesrghnrghrrgiivghlrdguvg X-ME-Proxy: Received: by mail.messagingengine.com (Postfix) with ESMTPA; Thu, 14 Oct 2021 19:38:03 -0400 (EDT) Date: Thu, 14 Oct 2021 16:38:02 -0700 From: Andres Freund To: Tom Lane Cc: Alvaro Herrera , Josef =?utf-8?B?xaBpbcOhbmVr?= , Dagfinn Ilmari =?utf-8?Q?Manns=C3=A5ker?= , Pg Hackers Subject: Re: [RFC] building postgres with meson Message-ID: <20211014233802.ungwz2qafz37eqna@alap3.anarazel.de> References: <202110141329.wrlws2i24syb@alvherre.pgsql> <20211014172412.rovmzox7dsahclis@alap3.anarazel.de> <906513.1634249338@sss.pgh.pa.us> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <906513.1634249338@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Hi, On 2021-10-14 18:08:58 -0400, Tom Lane wrote: > Andres Freund writes: > > Hm, so it seems we should make the test separately verify that perl -M{Opcode, > > ExtUtils::Embed, ExtUtils::ParseXS} doesn't fail, so that we can fail perl > > detection with a useful message? > > Our existing policy is that we should check this at configure time, > not later. Yea, I was thinking of configure (and meson's equivalent) as well. > Since plperl won't work at all without Opcode, it seems > appropriate to add a check there if you say --with-perl. I wasn't > aware that Red Hat had unbundled that from the minimal perl > installation :-(. > > OTOH, if they've not unbundled ExtUtils::Embed or ExtUtils::ParseXS, > I doubt it's worth the configure cycles to check for those separately. On debian the perl binary, with a sparse set of modules is in perl-base. ExtUtils::Embed and ExtUtils::ParseXS are in perl-modules-x.yy. Whereas Opcode is in libperlx.yy. But libperlx.yy depends on perl-modules-x.yy so I guess an Opcode.pm check would suffice. Seems we can just check all of them at once with with something like perl -MOpcode -MExtUtils::Embed -MExtUtils::ParseXSNotAvailable -e '' Can't locate ExtUtils/ParseXSNotAvailable.pm in @INC (you may need to install the ExtUtils::ParseXS3 module) (@INC contains: /home/andres/bin/perl5/lib/perl5/x86_64-linux-gnu-thread-multi /home/andres/bin/perl5/lib/perl5 /etc/perl /usr/local/lib/x86_64-linux-gnu/perl/5.32.1 /usr/local/share/perl/5.32.1 /usr/lib/x86_64-linux-gnu/perl5/5.32 /usr/share/perl5 /usr/lib/x86_64-linux-gnu/perl-base /usr/lib/x86_64-linux-gnu/perl/5.32 /usr/share/perl/5.32 /usr/local/lib/site_perl). Greetings, Andres Freund