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 1l07PR-0003tM-1I for pgsql-hackers@arkaria.postgresql.org; Thu, 14 Jan 2021 18:31:49 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1l07PP-000107-9c for pgsql-hackers@arkaria.postgresql.org; Thu, 14 Jan 2021 18:31:47 +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 1l07PP-000100-33 for pgsql-hackers@lists.postgresql.org; Thu, 14 Jan 2021 18:31:47 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1l07PN-0007Yp-0R for pgsql-hackers@postgresql.org; Thu, 14 Jan 2021 18:31:46 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.15.2/8.15.2) with ESMTP id 10EIVeYq1419200; Thu, 14 Jan 2021 13:31:41 -0500 From: Tom Lane To: Sergey Shinderuk cc: Thomas Munro , pgsql-hackers Subject: Re: pg_preadv() and pg_pwritev() In-reply-to: <1418166.1610647514@sss.pgh.pa.us> References: <341497.1608420857@sss.pgh.pa.us> <20201220224040.evr5pduibvm6dze5@alap3.anarazel.de> <448b3cb5-0ba0-6dc5-63c7-789e4eebc40b@postgrespro.ru> <1283127.1610554395@sss.pgh.pa.us> <1286060.1610558607@sss.pgh.pa.us> <1297389.1610562046@sss.pgh.pa.us> <1341608.1610580122@sss.pgh.pa.us> <1410650.1610638974@sss.pgh.pa.us> <1418166.1610647514@sss.pgh.pa.u! s> Comments: In-reply-to Tom Lane message dated "Thu, 14 Jan 2021 13:05:14 -0500" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <1419198.1610649100.1@sss.pgh.pa.us> Date: Thu, 14 Jan 2021 13:31:40 -0500 Message-ID: <1419199.1610649100@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk I wrote: > It seems like the more productive approach would be to try to identify > the right sysroot to use. I wonder if there is some less messy way > to find out the compiler's default sysroot than to scrape it out of > -v output. This is, of course, not terribly well documented by Apple. But Mr. Google suggests that "xcrun --show-sdk-path" might serve. What does that print for you? regards, tom lane