Re: [BUG?] macOS (Intel) build warnings: "ranlib: file … has no symbols" for aarch64 objects

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Peter Eisentraut <peter(at)eisentraut(dot)org>
Cc: Zhang Mingli <zmlpostgres(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: [BUG?] macOS (Intel) build warnings: "ranlib: file … has no symbols" for aarch64 objects
Date: 2026-02-04 15:28:53
Message-ID: 1453046.1770218933@sss.pgh.pa.us
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Peter Eisentraut <peter(at)eisentraut(dot)org> writes:
> On 29.01.26 07:35, Zhang Mingli wrote:
>> These warnings appear to be related to the recent AArch64 (pg_popcount)
>> optimization commits (possibly 79e232ca013c and fbe327e5b465d). It seems
>> that on my Intel-based macOS system, the build process is generating
>> empty or placeholder object files for the AArch64-specific implementations.
>> While there is no functional impact in my environment, I'm reporting
>> this to ensure it's noted, as other macOS/Intel users might encounter
>> the same warnings during their build.

> Probably not worth fixing, since this is an obsolescent platform.

Yeah. My Intel Mac buildfarm animal (longfin) has been showing this
for some time, but there's no corresponding warning on its ARM Mac
brethren (sifaka/indri). I doubt it's worth fixing just to get
rid of the warning. Although if a fix arises organically out of the
nearby thread about popcount refactoring, that would be okay here...

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2026-02-04 15:38:29 Re: Change copyObject() to use typeof_unqual
Previous Message Tom Lane 2026-02-04 15:18:50 Re: AIX support