public inbox for [email protected]
help / color / mirror / Atom feedFrom: Nathan Bossart <[email protected]>
To: Tom Lane <[email protected]>
Cc: John Naylor <[email protected]>
Cc: Peter Eisentraut <[email protected]>
Cc: Zhang Mingli <[email protected]>
Cc: PostgreSQL Hackers <[email protected]>
Subject: Re: [BUG?] macOS (Intel) build warnings: "ranlib: file … has no symbols" for aarch64 objects
Date: Tue, 28 Apr 2026 09:09:09 -0500
Message-ID: <afC_haf7bXWHb6e9@nathan> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>
<aYN5vmHb89m3sfgs@nathan>
<[email protected]>
<aYOTFLqyvvPUQLN8@nathan>
<ae7BvFTamKBDF1ga@nathan>
<[email protected]>
<ae7KiQcfDaavu5cD@nathan>
<ae-8WBrqoTWYCTCG@nathan>
<CANWCAZYFAP_fP0RSnor9Aa03aYAvQaM=+8oNeZSV432RNNynkQ@mail.gmail.com>
<[email protected]>
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
view thread (22+ messages) latest in thread
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: [email protected]
Cc: [email protected], [email protected], [email protected], [email protected], [email protected], [email protected]
Subject: Re: [BUG?] macOS (Intel) build warnings: "ranlib: file … has no symbols" for aarch64 objects
In-Reply-To: <afC_haf7bXWHb6e9@nathan>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox