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 1nu3S1-00028x-73 for pgsql-hackers@arkaria.postgresql.org; Thu, 26 May 2022 02:42:13 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1nu3Rz-0007AU-9A for pgsql-hackers@arkaria.postgresql.org; Thu, 26 May 2022 02:42:11 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1nu3Rx-000758-A3 for pgsql-hackers@lists.postgresql.org; Thu, 26 May 2022 02:42:10 +0000 Received: from wout5-smtp.messagingengine.com ([64.147.123.21]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1nu3Rt-000200-AC for pgsql-hackers@postgresql.org; Thu, 26 May 2022 02:42:08 +0000 Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailout.west.internal (Postfix) with ESMTP id E76523200943; Wed, 25 May 2022 22:42:01 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute3.internal (MEProxy); Wed, 25 May 2022 22:42:02 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=anarazel.de; h= cc:cc:content-type:date:date:from:from:in-reply-to:in-reply-to :message-id:mime-version:references:reply-to:sender:subject :subject:to:to; s=fm1; t=1653532921; x=1653619321; bh=BgpBqBbvgR sLC7Ezzdiox4uolamEvJP0gm1bnYLsWxM=; b=s/Rpi3VK8Hxv9bsSNN/RRCgRg0 GCNdilGejoSIGsHhOiOLxJUawUEV/iRCT6tCT6mcEkWnmIAA8ResehqEUtR/vx02 Gj65lIx7jxAFe5KtpOS51fzip7VO9EsiFb70Vhja5tG9SX98qlCsoSlGTjOu64qH 0b+fm6+Gv4FeEobIOhgDz2w9iOlV8fTY/SONkR/ky0CoKTLOG7BG3rzVchIcoA/l QSPI31tQ9OoNomqMPBKjqXA4qkbflPoINP0Z310Jl9FCI27fvNt3jZCYovIB52I0 /JPCz4Tp5ziJJK5JimpprOykiApazWVE16vFgukS8KOMzxaeFyvMcGkEcORA== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-type:date:date:feedback-id :feedback-id: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=1653532921; x=1653619321; bh=BgpBqBbvgRsLC7Ezzdiox4uolamE vJP0gm1bnYLsWxM=; b=K31u+yRIWUzhPXq9A4a7DITLIbbvXQyGWbQUGH6g52ZZ 4TRx0avBk4Pqn7ARnkZ98Jh6/CU2/o55XuFLG6fWfkB2BUnW4sSGpJ7Y0ZjCGWxO X7oKPDubxbtN9ekvvazPyoP/wVELnMkwctHgB6HmS33O/iYuGP77m5syZTLEqduB xAdRZaD7lD8XUUonhJ6QOouEdL8JZWvfWTQ6FAzEs/HfLohpZO7tz/9vPf+WiBsj nTHwPRkYdduy3aTM8LWySzmsEwbBKcy+1lthTmfTWi7ThNg0GqzneM1bKmW73v7B AZ5jerdUvWLHWEfSy88UMRZqu8WohyukaLFZ2ePiAw== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvfedrjeeigdeiudcutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecunecujfgurhepfffhvfevuffkfhggtggujgesthdtre dttddtvdenucfhrhhomheptehnughrvghsucfhrhgvuhhnugcuoegrnhgurhgvshesrghn rghrrgiivghlrdguvgeqnecuggftrfgrthhtvghrnhepvdfffeevhfetveffgeeiteefhf dtvdffjeevhfeuteegleduheetveduieettddunecuvehluhhsthgvrhfuihiivgeptden ucfrrghrrghmpehmrghilhhfrhhomheprghnughrvghssegrnhgrrhgriigvlhdruggv X-ME-Proxy: Feedback-ID: id4a34324:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Wed, 25 May 2022 22:42:00 -0400 (EDT) Date: Wed, 25 May 2022 19:41:59 -0700 From: Andres Freund To: Tom Lane Cc: pgsql-hackers@postgresql.org Subject: Re: [RFC] building postgres with meson Message-ID: <20220526024159.d72mg3rvrlj7h5kv@alap3.anarazel.de> References: <20211012083721.hvixq4pnh2pixr3j@alap3.anarazel.de> <20220526004731.km2ykossewzramt3@alap3.anarazel.de> <2071393.1653529113@sss.pgh.pa.us> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <2071393.1653529113@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Hi, On 2022-05-25 21:38:33 -0400, Tom Lane wrote: > Andres Freund writes: > > in the meson unconference session you'd spotted flex flags for psqlscanslash.l > > (I think) being "hardcoded". As far as I can tell that's largely just copied > > from the Makefile): > > > src/backend/parser/Makefile:scan.c: FLEXFLAGS = -CF -p -p > > src/backend/utils/adt/Makefile:jsonpath_scan.c: FLEXFLAGS = -CF -p -p > > src/bin/psql/Makefile:psqlscanslash.c: FLEXFLAGS = -Cfe -p -p > > src/fe_utils/Makefile:psqlscan.c: FLEXFLAGS = -Cfe -p -p > > Hmm, OK. There *is* a FLEXFLAGS definition supplied by configure, and > I believe many of our scanners do use it, but evidently we're just > overriding it for the ones where we really care about using specific > flags. It also looks like the configure-supplied version is usually > empty, so the fact that this variable exists may be mostly a holdover > from Autoconf practice rather than something we ever cared about. Yea, it looks like that. ISTM that it'd still be good to have something like FLEXFLAGS. But it doesn't look great, nor really intentional, that FLEXFLAGS is overwritten rather than appended? > I think the main thing I didn't like about the way you have it in the > meson file is the loss of greppability. I could investigate this > question in a few seconds just now, but if we drop the use of > FLEXFLAGS as a macro it'll become much harder to figure out which > places use what. I disliked a bunch of repetitiveness as I had it, so I'm polishing that part just now. What would you want to grep for? Places that specify additional flags? Or just places using flex? Greetings, Andres Freund