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 1lzdzQ-0006OQ-VX for pgsql-hackers@arkaria.postgresql.org; Sat, 03 Jul 2021 11:39:17 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1lzdzM-00078P-Kg for pgsql-hackers@arkaria.postgresql.org; Sat, 03 Jul 2021 11:39:12 +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 1lzdzL-00078E-Ta for pgsql-hackers@lists.postgresql.org; Sat, 03 Jul 2021 11:39:12 +0000 Received: from forward1-smtp.messagingengine.com ([66.111.4.223]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1lzdzB-0005Tj-0j for pgsql-hackers@lists.postgresql.org; Sat, 03 Jul 2021 11:39:09 +0000 Received: from compute6.internal (compute6.nyi.internal [10.202.2.46]) by mailforward.nyi.internal (Postfix) with ESMTP id DF41B194070D; Sat, 3 Jul 2021 07:38:57 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute6.internal (MEProxy); Sat, 03 Jul 2021 07:38:57 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding: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=fm3; bh=N2mrH81tIGsnEN7W9xaVKGE/AjI87a5G9P3Ia2Qen qk=; b=Y/TopbmjEfbY94XJ+b5pyjldfwEVIg/k+jKCYdjuKV0Ybqy4EhJ1WjsNz 7hxdqM2OOAdZOXD/Uf1H7ifXaMD0hLRML/ouRMDBKASkqn+N21fct+OBxpk7QDML l/K+8Pa9UYELiDYbzpBPNm/FkF447j39NMjM9KDjpJvJCL43jd57cuLULDyFCuLG +tJKk9AU+B+kUskqCyuq4dkYhrilwO1JzmCOq/dHQ0+ADDbtFPBpkLQjwvBmdcwv KWR9m6aDu2ni/Y+n+lMJd/WxFf9aF4tT7xYc6c28x3Pw6k/Z0fvTQUPEqwDfEQ2K yXL93fyeX0AfsiR6uqmk5ZME/M6YQ== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduledrfeejtddggeduucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhepuffvfhfhkffffgggjggtgfesthejredttdefjeenucfhrhhomheprfgvthgv rhcugfhishgvnhhtrhgruhhtuceophgvthgvrhdrvghishgvnhhtrhgruhhtsegvnhhtvg hrphhrihhsvggusgdrtghomheqnecuggftrfgrthhtvghrnhepleevheehueeiudeiteei tdekueetleefteejffeiffdugedvffdvffdtiedvueeknecuvehluhhsthgvrhfuihiivg eptdenucfrrghrrghmpehmrghilhhfrhhomhepphgvthgvrhdrvghishgvnhhtrhgruhht segvnhhtvghrphhrihhsvggusgdrtghomh X-ME-Proxy: Received: by mail.messagingengine.com (Postfix) with ESMTPA; Sat, 3 Jul 2021 07:38:55 -0400 (EDT) Subject: Re: [PATCH v3 1/1] Fix detection of preadv/pwritev support for OSX. To: Thomas Munro , Sandeep Thakkar Cc: Dave Page , Tom Lane , James Hilliard , David Steele , PostgreSQL Hackers , Sergey Shinderuk References: <20210122193230.25295-1-james.hilliard1@gmail.com> <2781003.1617083917@sss.pgh.pa.us> From: Peter Eisentraut Message-ID: <6ac601c7-9a72-d354-cfaa-03a66108c778@enterprisedb.com> Date: Sat, 3 Jul 2021 13:38:53 +0200 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:78.0) Gecko/20100101 Thunderbird/78.11.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On 21.06.21 07:22, Thomas Munro wrote: > I'm not personally against the proposed change. I'll admit there is > something annoying about Apple's environment working in a way that > doesn't suit traditional configure macros that have been the basis of > portable software for a few decades, but when all's said and done, > configure is a Unix wars era way to make things work across all the > Unixes, and most of them are long gone, configure itself is on the way > out, and Apple's still here, so... I think this change is perfectly appropriate (modulo some small cleanups). The objection was that you cannot reliably use AC_CHECK_FUNCS (and therefore AC_REPLACE_FUNCS) anymore, but that has always been true, since AC_CHECK_FUNCS doesn't handle macros, compiler built-ins, and functions that are not declared, and any other situation where looking for a symbol in a library is not the same as checking whether the symbol actual works for your purpose. This is not too different from the long transition from "does this header file exists" to "can I compile this header file". So in fact the correct way forward would be to get rid of all uses of AC_CHECK_FUNCS and related, and then this problem goes away by itself.