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 1mmha2-00089Y-1X for pgsql-hackers@arkaria.postgresql.org; Mon, 15 Nov 2021 19:23:50 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1mmha0-0000ZU-50 for pgsql-hackers@arkaria.postgresql.org; Mon, 15 Nov 2021 19:23:48 +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 1mmhZz-0000ZH-24 for pgsql-hackers@lists.postgresql.org; Mon, 15 Nov 2021 19:23:47 +0000 Received: from wout5-smtp.messagingengine.com ([64.147.123.21]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1mmhZw-0005F8-49 for pgsql-hackers@postgresql.org; Mon, 15 Nov 2021 19:23:45 +0000 Received: from compute5.internal (compute5.nyi.internal [10.202.2.45]) by mailout.west.internal (Postfix) with ESMTP id F03E13201CED; Mon, 15 Nov 2021 14:23:41 -0500 (EST) Received: from mailfrontend1 ([10.202.2.162]) by compute5.internal (MEProxy); Mon, 15 Nov 2021 14:23:42 -0500 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=fm3; bh=vQWBQgm72MQ0esVUH1Wf5zqTYTy 7ux7Gn8RyRdlsFDo=; b=uDuYSo2LMgm+lv0GsEUsLoO+A8hIcrRHwrBzoeMe6M2 qPfCZ2PCqN5OnFMVIhFSfJqllt0LFQ+0UsyUrHgy1OElxgbuowW4vKlbRsu6NQmq 1vULmw9/Tjx4rjvAJcXEtLZ/KLuM7ompdKOZWnkayQ6hIExpkIQmdO8QNZc4ZNDp GrAHwa2Pjz/vAkgLB22sdh1M91H0AbWnQKFUwixBa5WCqMS4whoY+f+Eh5il73e4 4FJ2TqcLDX9WnEmkN/xbdSqH5zPeiaabZpQJA5FB1Tr2ObQo8TBzyUqdhBf2P93q Mu6uF8vCdwbciuFlGuT6POmDrw+dYlZIaRZqfCLIMew== 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=vQWBQg m72MQ0esVUH1Wf5zqTYTy7ux7Gn8RyRdlsFDo=; b=fAkN1T8xSWLnhSmSQxwXXx zfLkDkOEGwrJp8zryTVAC8l6v4pd7G7iR6DoB9DPfnYbHzoDwSnIornSATTZK/Br tWrlO67CGBR8vUuYquqfUnqKtxm7xaEDqkQ7jbfemf3RxmtgOSMMv00gmUYV1kLN eoKo3vA0Np6mgtIFHjc394tGkqpzVlxykx+h6fxTBT44CUfwExt0/83be38ZmHaG MlUqLISb0OedVcHkaX1PVHNi68z4LRpWLjW2cXyq2DmdvFPj8QGfytoS84uAKcHo caoebD33rpeDeAkqYmDc21UT60I9eOTLHEgCuG1RMdss/mj5tuIuhUUciPLX0w/g == X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvuddrfedtgdeljecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecunecujfgurhepfffhvffukfhfgggtuggjsehttdertd dttddvnecuhfhrohhmpeetnhgurhgvshcuhfhrvghunhguuceorghnughrvghssegrnhgr rhgriigvlhdruggvqeenucggtffrrghtthgvrhhnpedukefhkeelueegveetheelffffje egleeuudelfeefuedtleffueejfffhueffudenucevlhhushhtvghrufhiiigvpedtnecu rfgrrhgrmhepmhgrihhlfhhrohhmpegrnhgurhgvshesrghnrghrrgiivghlrdguvg X-ME-Proxy: Received: by mail.messagingengine.com (Postfix) with ESMTPA; Mon, 15 Nov 2021 14:23:41 -0500 (EST) Date: Mon, 15 Nov 2021 11:23:40 -0800 From: Andres Freund To: Tom Lane Cc: pgsql-hackers@postgresql.org Subject: Re: [RFC] building postgres with meson Message-ID: <20211115192340.xoaddx5nwiu2ftud@alap3.anarazel.de> References: <20211012083721.hvixq4pnh2pixr3j@alap3.anarazel.de> <20211115183415.gkcx4akz7vmsvgik@alap3.anarazel.de> <2145728.1637003485@sss.pgh.pa.us> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <2145728.1637003485@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Hi, On 2021-11-15 14:11:25 -0500, Tom Lane wrote: > Andres Freund writes: > > One important thing to call out: Meson has support for the AIX linker, but > > *not* the xlc compiler. I.e. one has to use gcc (or clang, but I didn't > > try). I don't know if we'd require adding support for xlc to meson - xlc is > > pretty buggy and it doesn't seem particularly crucial to support such an old > > crufty compiler on a platform that's not used to a significant degree? > > While I have no particular interest in AIX or xlc specifically, I do > worry about us becoming a builds-on-gcc-or-workalikes-only project. > I suppose MSVC provides a little bit of a cross-check, but I don't > really like giving up on other compilers. Discounting gcc+clang+MSVC > leaves just a few buildfarm animals, and the xlc ones are a significant > part of that population. Yea, that's a reasonable concern. I wonder if there's some non-mainstream compiler that actually works on, um, more easily available platforms that we could utilize. > (In fact, unless somebody renews fossa/husky's > icc license, the three xlc animals will be an outright majority of > them, because wrasse and anole are the only other active animals with > non-mainstream compilers.) It should probably be doable to get somebody to run another icc animal. Icc is supported by meson, fwiw. > Having said that, I don't plan to be the one trying to get meson > to add xlc support ... It'd probably not be too hard. But given that it's quite hard to get access to AIX + xlc, I'm not sure it's something I want to propose. There's no resources to run halfway regular tests on that I found... It's good to make sure we're not growing too reliant on some compiler(s), but imo only really makes sense if the alternative compilers are meaningfully available and maintained. Greetings, Andres Freund