| From: | Nathan Bossart <nathandbossart(at)gmail(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | John Naylor <johncnaylorls(at)gmail(dot)com>, Peter Eisentraut <peter(at)eisentraut(dot)org>, 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-04-28 14:09:09 |
| Message-ID: | afC_haf7bXWHb6e9@nathan |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Apr 28, 2026 at 09:29:41AM -0400, Tom Lane wrote:
> If we do care, a low-tech solution could be to have a dummy symbol
> declared in each file, along the lines of
>
> #if HAVE_X86_64_POPCNTQ
> // code for popcntq case
> #elif HAVE_FROBNITZ
> // code for frobnitz case
> ...
> #else
> /* prevent linker complaints about empty module */
> extern int pg_cpu_x86_dummy_variable;
> int pg_cpu_x86_dummy_variable = 0;
> #endif
>
> Actually then we'd not need to change the build systems either...
I've been trying to avoid doing that, but it's a far simpler solution, and
in theory it should fix the problem for all platforms, too. So, it's
probably the way to go.
--
nathan
| Attachment | Content-Type | Size |
|---|---|---|
| v3-0001-avoid-ranlib-warnings-on-macOS.patch | text/plain | 1.8 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dilip Kumar | 2026-04-28 14:16:13 | Re: Proposal: Conflict log history table for Logical Replication |
| Previous Message | Ayush Tiwari | 2026-04-28 13:34:52 | Re: [PATCH] Fix stale relation close in sequence synchronization |