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 1nC1k7-00080X-3r for pgsql-hackers@arkaria.postgresql.org; Mon, 24 Jan 2022 15:58:55 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1nC1k5-0003ET-OK for pgsql-hackers@arkaria.postgresql.org; Mon, 24 Jan 2022 15:58:53 +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 1nC1k5-0003EJ-Em for pgsql-hackers@lists.postgresql.org; Mon, 24 Jan 2022 15:58:53 +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 1nC1k2-000148-Dh for pgsql-hackers@lists.postgresql.org; Mon, 24 Jan 2022 15:58:52 +0000 Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailout.west.internal (Postfix) with ESMTP id 42C943201FD3; Mon, 24 Jan 2022 10:58:49 -0500 (EST) Received: from mailfrontend2 ([10.202.2.163]) by compute3.internal (MEProxy); Mon, 24 Jan 2022 10:58:49 -0500 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; bh=wPSq9FRKKh58VKd+n02Zk53iNvp0caMQkbkEtSbi4 4c=; b=TWIMTvW8/FjEMIcAxPv2Kd7jWyihxCqETwHhZ7RfGQuELa6zHil5MGKGp jRYeQie2yALvYu49kR92zpH3yTOYAkakzZT1fbkLd+xWFsEl4feRkbrqwcSRJWfS /cefkFYITBnzG7nmnWKvBD8umtNmTJDSo0/DhjSD9j5RmRWFdA+Qqn6ETzMTycBx NpUL1mjD+5Qceqn6FKswOavDWWBvswS4OE4g9uB6hBAIVGa8H5oHycWA4JSVHwHA t3T99mQ0byG0r7wlq+wwdiZIm7DJ7r0YB2c+a7H1SHaXNlfUZN5Gx/FygdrK/Jn7 zUPod5oGhkwMS/uIpUen8obtnyZWg== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvvddrvdeigdekhecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecunecujfgurhepkfffgggfuffvfhfhjggtgfesthejre dttdefjeenucfhrhhomheprfgvthgvrhcugfhishgvnhhtrhgruhhtuceophgvthgvrhdr vghishgvnhhtrhgruhhtsegvnhhtvghrphhrihhsvggusgdrtghomheqnecuggftrfgrth htvghrnhepuddtfeejheegtedtgeehjefffefhffduheekheefieetveeljeeuleevueeh tedvnecuffhomhgrihhnpehgnhhurdhorhhgnecuvehluhhsthgvrhfuihiivgeptdenuc frrghrrghmpehmrghilhhfrhhomhepphgvthgvrhdrvghishgvnhhtrhgruhhtsegvnhht vghrphhrihhsvggusgdrtghomh X-ME-Proxy: Received: by mail.messagingengine.com (Postfix) with ESMTPA; Mon, 24 Jan 2022 10:58:46 -0500 (EST) Message-ID: <479f88d9-f961-e705-e1bf-5068272f7c91@enterprisedb.com> Date: Mon, 24 Jan 2022 16:58:46 +0100 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:91.0) Gecko/20100101 Thunderbird/91.5.0 Subject: Re: PSA: Autoconf has risen from the dead Content-Language: en-US To: Tom Lane Cc: pgsql-hackers@lists.postgresql.org References: <1627398.1642955357@sss.pgh.pa.us> <652d5f5d-27e7-b1db-03e0-c74cfdca40cd@enterprisedb.com> <1871565.1643033667@sss.pgh.pa.us> From: Peter Eisentraut In-Reply-To: <1871565.1643033667@sss.pgh.pa.us> 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 24.01.22 15:14, Tom Lane wrote: > Do these versions fix any bugs that affect us (i.e., that we've > not already created workarounds for)? The only thing that could be of interest is that the workaround we are carrying in config/check_decls.m4 was originally upstreamed by Noah, but was then later partially reverted and replaced by a different solution. Further explanation is here: https://git.savannah.gnu.org/cgit/autoconf.git/commit/?id=ec90049dfcf4538750e61d675d885157fa5ca7f8 I don't think it has affected us in practice, though.