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

Tom Lane <tgl@sss.pgh.pa.us>

From: Tom Lane <tgl@sss.pgh.pa.us>
To: Peter Eisentraut <peter@eisentraut.org>
Cc: Nathan Bossart <nathandbossart@gmail.com>, John Naylor <johncnaylorls@gmail.com>, Zhang Mingli <zmlpostgres@gmail.com>, PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Date: 2026-04-29T13:58:58Z
Lists: pgsql-hackers
Peter Eisentraut <peter@eisentraut.org> writes:
> On 28.04.26 22:32, Nathan Bossart wrote:
>> Here's a full set of patches for back-patching purposes.
>> protocol_openssl.c has a similar problem on older versions.  I suppose this
>> is the sort of thing I could back-patch all the way to v9.2.  Does anyone
>> feel strongly one way or the other about that?

> Why should this be backpatched at all?

To silence those warnings.  If you're using a Mac for development,
they're pretty annoying.  And we have generally had a policy of
trying to silence warnings in still-interesting branches.

			regards, tom lane



Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →
  1. Suppress "has no symbols" linker warnings on macOS.

  2. Fix two error messages in extended_stats_funcs.c