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.96) (envelope-from ) id 1wHBYa-006w7t-2A for pgsql-hackers@arkaria.postgresql.org; Mon, 27 Apr 2026 02:18:45 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.96) (envelope-from ) id 1wHBYZ-00BkG7-1R for pgsql-hackers@arkaria.postgresql.org; Mon, 27 Apr 2026 02:18:43 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1wHBYZ-00BkFw-0W for pgsql-hackers@lists.postgresql.org; Mon, 27 Apr 2026 02:18:43 +0000 Received: from sss.pgh.pa.us ([68.162.161.243]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.98.2) (envelope-from ) id 1wHBYW-00000002xQt-42y8 for pgsql-hackers@lists.postgresql.org; Mon, 27 Apr 2026 02:18:42 +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 63R2IXiQ2446900; Sun, 26 Apr 2026 22:18:33 -0400 From: Tom Lane To: Nathan Bossart cc: Peter Eisentraut , Zhang Mingli , PostgreSQL Hackers Subject: =?UTF-8?Q?Re:_[BUG=3F]_macOS_(Intel)_build_warnings:_"ranlib:_fil?= =?UTF-8?Q?e_=E2=80=A6_has_no_symbols"_for_aarch64_objects?= In-reply-to: References: <229aaaf3-f529-44ed-8e50-00cb6909af21@Spark> <4df5af1a-8528-4f9f-9daf-ec069bd66f69@eisentraut.org> <1453046.1770218933@sss.pgh.pa.us> <1472307.1770229663@sss.pgh.pa.us> Comments: In-reply-to Nathan Bossart message dated "Sun, 26 Apr 2026 20:54:04 -0500" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <2446898.1777256313.1@sss.pgh.pa.us> Date: Sun, 26 Apr 2026 22:18:33 -0400 Message-ID: <2446899.1777256313@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Nathan Bossart writes: > Well, the latest macOS update added these warnings for aarch64: > ranlib: warning: 'libpgport_shlib.a(pg_cpu_x86.c.o)' has no symbols > ranlib: warning: 'libpgport_shlib.a(pg_popcount_x86.c.o)' has no symbols > ranlib: warning: 'libpgport_shlib.a(pg_cpu_x86.c.o)' has no symbols > ranlib: warning: 'libpgport_shlib.a(pg_popcount_x86.c.o)' has no symbols > I'm not seeing an easy way to pass -no_warning_for_no_symbols to ranlib, at > least with meson. Hm... Yeah, we aren't even calling ranlib directly, it goes through 'ar' which doesn't expose any such option. In any case that'd necessarily be an OS-specific option. I previously suggested that we should teach the build systems not to build the foo_x86 and foo_aarch64 modules when not on those architectures. That was shot down for reasons that made no great amount of sense to me, but I think it'd be fairly easy and clean. regards, tom lane