Re: Annoying build warnings from latest Apple toolchain

Robert Haas <robertmhaas(at)gmail(dot)com> writes:
> On Mon, Nov 20, 2023 at 3:53 PM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> 13.6.2? longfin's host is on 13.6.1, and the only thing Software
>> Update is showing me is an option to upgrade to Sonoma. But anyway...

> Uh, I guess Apple made a special version just for me? That's
> definitely what it says.

Might be for M-series only; longfin's host is still Intel.

>> Hmm ... I fixed these things in the autoconf build: neither my
>> buildfarm animals nor manual builds show any warnings. I thought
>> the problems weren't there in the meson build. Need to take another
>> look I guess.

> They're definitely there for me, and there are a whole lot of them. I
> would have thought that if they were there for you in the meson build
> you would have noticed, since ninja suppresses a lot of distracting
> output that make prints.

I'm generally still using autoconf, I only run meson builds when
somebody complains about them ;-). But yeah, I see lots of
"ld: warning: -undefined error is deprecated" when I do that.
This seems to have been installed by Andres' 9a95a510a:

ldflags += ['-isysroot', pg_sysroot]
+ # meson defaults to -Wl,-undefined,dynamic_lookup for modules, which we
+ # don't want because a) it's different from what we do for autoconf, b) it
+ # causes warnings starting in macOS Ventura
+ ldflags_mod += ['-Wl,-undefined,error']

The autoconf side seems to just be letting this option default.
I'm not sure what the default choice is, but evidently it's not
"-undefined error"? Or were they stupid enough to not allow you
to explicitly select the default behavior?

Also, I *don't* see any complaints about duplicate libraries.
What build options are you using?

regards, tom lane