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

Nathan Bossart <nathandbossart(at)gmail(dot)com> writes:
> Well, the latest macOS update added these warnings for aarch64:
> ranlib: warning: 'libpgport_shlib.a(pg_cpu_x86.c.o)' has no symbols
> ranlib: warning: 'libpgport_shlib.a(pg_popcount_x86.c.o)' has no symbols
> ranlib: warning: 'libpgport_shlib.a(pg_cpu_x86.c.o)' has no symbols
> ranlib: warning: 'libpgport_shlib.a(pg_popcount_x86.c.o)' has no symbols

> I'm not seeing an easy way to pass -no_warning_for_no_symbols to ranlib, at
> least with meson. Hm...

Yeah, we aren't even calling ranlib directly, it goes through 'ar'
which doesn't expose any such option. In any case that'd necessarily
be an OS-specific option.

I previously suggested that we should teach the build systems not
to build the foo_x86 and foo_aarch64 modules when not on those
architectures. That was shot down for reasons that made no great
amount of sense to me, but I think it'd be fairly easy and clean.

regards, tom lane