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 1nqcwY-0004Ci-PM for pgsql-hackers@arkaria.postgresql.org; Mon, 16 May 2022 15:47:34 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1nqcwX-0001jc-Mi for pgsql-hackers@arkaria.postgresql.org; Mon, 16 May 2022 15:47:33 +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 1nqcwX-0001jL-DA for pgsql-hackers@lists.postgresql.org; Mon, 16 May 2022 15:47:33 +0000 Received: from wout1-smtp.messagingengine.com ([64.147.123.24]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1nqcwU-0000dQ-Fh for pgsql-hackers@postgresql.org; Mon, 16 May 2022 15:47:32 +0000 Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.west.internal (Postfix) with ESMTP id 85C6D32003D3; Mon, 16 May 2022 11:47:28 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute1.internal (MEProxy); Mon, 16 May 2022 11:47:28 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-transfer-encoding :content-type:date:date:from:from:in-reply-to:in-reply-to :message-id:mime-version:references:reply-to:sender:subject :subject:to:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm1; t=1652716048; x=1652802448; bh=TEYxv2vAifiHk 8EhZZe0TC18OTsg8+svqwrDFPIPy0g=; b=RClHirrMJ0k2VNA5aL1vlWTP5j+vA 7IwjYnhJbVMQh4RbTvmtMk/KZ5fFiNQN17BVdRLvpWhBTxMP4RThh6v/VSIV07QE 6AtK0LARmr76CjJ/jYDDLFxAICrhFqhQkw89LsKZdmAP4ciY+hkZnLJSYAhw6ap4 DUnoNkeXwLvYLCBlK/JfRCOdqHHoA6aWUqjKk22ZFui/qeknCqcEE7Nf8mMrTQyU UNHJiQSfh9O22v1AbfR8fNqlm2y8zYiAAW4Amwpq+irv4QF3OpVWB41NDO2scurs qpc0PWKLcddW0c2uEQwwj7EL/4kSZrzKvJ4eK74mQi3ex2AM6nnRSnwnw== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvfedrheehgdeludcutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenuc fjughrpefkffggfgfuvfevfhfhjggtgfesthejredttdefjeenucfhrhhomheprfgvthgv rhcugfhishgvnhhtrhgruhhtuceophgvthgvrhdrvghishgvnhhtrhgruhhtsegvnhhtvg hrphhrihhsvggusgdrtghomheqnecuggftrfgrthhtvghrnhepheelffeggedujeetiefh leetuddvieffhfffvdejvdffgeejkeduleduheduieefnecuvehluhhsthgvrhfuihiivg eptdenucfrrghrrghmpehmrghilhhfrhhomhepphgvthgvrhdrvghishgvnhhtrhgruhht segvnhhtvghrphhrihhsvggusgdrtghomh X-ME-Proxy: Received: by mail.messagingengine.com (Postfix) with ESMTPA; Mon, 16 May 2022 11:47:25 -0400 (EDT) Message-ID: <09886ba4-727a-2048-42de-27c07ad9b3c3@enterprisedb.com> Date: Mon, 16 May 2022 17:47:24 +0200 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:91.0) Gecko/20100101 Thunderbird/91.9.0 Subject: Re: [RFC] building postgres with meson -v8 Content-Language: en-US To: Andres Freund Cc: pgsql-hackers@postgresql.org References: <498f4933-7fa9-6815-7574-1d3b2ec85daf@dunslane.net> <1037188.1648508299@sss.pgh.pa.us> <20220328231140.7ylalxc76zli6p46@alap3.anarazel.de> <20f604f6-40be-e17b-87ac-32737743c63d@enterprisedb.com> <20220429174633.6io23mlwphdqdakv@alap3.anarazel.de> <8ced34e6-7abf-b3b2-3770-0487794753c5@enterprisedb.com> <20220502163602.smlwfhh2cnutxora@alap3.anarazel.de> <20220512193053.kbmeaszrjs73zmox@alap3.anarazel.de> From: Peter Eisentraut In-Reply-To: <20220512193053.kbmeaszrjs73zmox@alap3.anarazel.de> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On 12.05.22 21:30, Andres Freund wrote: > On 2022-05-11 12:18:58 +0200, Peter Eisentraut wrote: >> I fixed the Perl detection issue in my macOS environment that I had reported >> a while ago. > > Hm. I wonder if it's right to check with is_file() - perhaps there are > platforms that have split off the include directory? The existing code uses "test -f", so using is_file() would keep it working the same way. >> After that, these configure options don't have an equivalent yet: >> >> --disable-rpath >> --enable-profiling >> --disable-thread-safety >> --with-libedit-preferred >> >> The first three overlap with meson built-in functionality, so we would need >> to check whether the desired functionality is available somehow. > > Which builtin functionality does --enable-profiling overlap with? There's a > coverage option, perhaps you were thinking of that? I saw an option about "profile guided optimization" (b_pgo), which seems possibly related. > I don't think we should add --disable-thread-safety, platforms without it also > aren't going to support ninja / meson... IIRC Thomas was planning to submit a > patch getting rid of it independently... sure >> From 049b34b6a8dd949f0eb7987cad65f6682a6ec786 Mon Sep 17 00:00:00 2001 >> From: Peter Eisentraut >> Date: Wed, 11 May 2022 09:06:13 +0200 >> Subject: [PATCH 3/9] meson: prereq: Refactor dtrace postprocessing make rules >> >> Move the dtrace postprocessing sed commands into a separate file so >> that it can be shared by meson. Also split the rule into two for >> proper dependency declaration. > > Hm. Using sed may be problematic on windows... This code is only used when dtrace is enabled, which probably doesn't apply on Windows.