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 1vnhbW-00ATFZ-1W for pgsql-hackers@arkaria.postgresql.org; Wed, 04 Feb 2026 18:27:54 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.96) (envelope-from ) id 1vnhbU-00D4Hw-1z for pgsql-hackers@arkaria.postgresql.org; Wed, 04 Feb 2026 18:27:52 +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 1vnhbU-00D4Ho-11 for pgsql-hackers@lists.postgresql.org; Wed, 04 Feb 2026 18:27:52 +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 1vnhbR-00000000YyX-2XJn for pgsql-hackers@lists.postgresql.org; Wed, 04 Feb 2026 18:27:51 +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 614IRhul1472308; Wed, 4 Feb 2026 13:27:43 -0500 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> Comments: In-reply-to Nathan Bossart message dated "Wed, 04 Feb 2026 10:54:22 -0600" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <1472306.1770229663.1@sss.pgh.pa.us> Date: Wed, 04 Feb 2026 13:27:43 -0500 Message-ID: <1472307.1770229663@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Nathan Bossart writes: > Hm. The options I see for fixing this seem to be: > * Pass -no_warning_for_no_symbols flag on this platform, but that option > might not be available in older toolchains. > * Add a random symbol to this file. That seems like a hack. > * Add build logic to only compile this file when necessary. I've been > trying to get rid of complexity here, so this feels like a step backwards. > IMHO none of these options seem worth the effort to fix a warning on an > obsolescent platform, so my vote is to do nothing for now. The idea I'd had was to simply merge pg_popcount_aarch64.c and pg_popcount_x86.c into one file. Since each one is basically one giant #ifdef block conditioned on a different symbol, they'd not interfere. But I wouldn't propose this unless it made sense from a code-structure viewpoint, and I'm not sure it does. It could make sense if there was some code that could be shared, but I'm not seeing much. regards, tom lane