Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1tzhFU-005MPu-0T for pgsql-hackers@arkaria.postgresql.org; Tue, 01 Apr 2025 19:26:12 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1tzhFR-005asU-Pz for pgsql-hackers@arkaria.postgresql.org; Tue, 01 Apr 2025 19:26:09 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1tzhFR-005asL-E3 for pgsql-hackers@lists.postgresql.org; Tue, 01 Apr 2025 19:26:09 +0000 Received: from sss.pgh.pa.us ([68.162.161.243]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1tzhFM-002oYC-0S for pgsql-hackers@lists.postgresql.org; Tue, 01 Apr 2025 19:26:09 +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 531JPxMV407465; Tue, 1 Apr 2025 15:25:59 -0400 From: Tom Lane To: Peter Eisentraut cc: pgsql-hackers@lists.postgresql.org Subject: Re: macOS 15.4 versus strchrnul() In-reply-to: References: <385134.1743523038@sss.pgh.pa.us> Comments: In-reply-to Peter Eisentraut message dated "Tue, 01 Apr 2025 19:07:02 +0200" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <407463.1743535559.1@sss.pgh.pa.us> Date: Tue, 01 Apr 2025 15:25:59 -0400 Message-ID: <407464.1743535559@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Peter Eisentraut writes: > On 01.04.25 17:57, Tom Lane wrote: >> I speculate that the meson test for preadv/pwritev has never worked >> for macOS either, and we haven't noticed because nobody has tried to >> build with meson on a machine with low enough default deployment >> target to not have preadv/pwritev. > Agreed. Attached is a patch that implements the test more along the > lines of how Autoconf does it. This gives correct results for me for > strchrnul() in various configurations. Cool. Let me try it here, and I'll push if no problems arise. > Btw., I see on the buildfarm that strchrnul() is also available on > FreeBSD, DragonFly BSD, NetBSD, and musl (Alpine Linux). So perhaps > some of the comments ought to be rewritten away from that it's a > glibc-specific extension. OK, will do something about that --- maybe like "originally glibc specific, but later adopted by other platforms"? regards, tom lane