Carlo Cabrera

> Perhaps this only works when it is linked? That too, but not exactly. There's some weird [`Makefile` logic](https://github.com/postgres/postgres/blob/c9818798147a4eec00bba61a05fa9bc88398ec3b/src/Makefile.global.in#L103-L142) that scans the prefix for the string `postgresql` and inserts `postgresql`...

That needs to be backported to the earlier versions, as they'll have broken `pg_config` binaries too.

Seems to crash when it tries to run `vtkpython`.

I don't mind keeping it on `[email protected]`. But if you're keen to backport the patch, I'm okay with that too.

@Bo98 might have a better idea about the [Big Sur-only `swift` errors](https://github.com/Homebrew/homebrew-core/actions/runs/2863253359). Trying a different `swift` seems worth a shot in the meantime.

Same error, but it's still making use of Xcode `swift`.

The issue might be in the SDK, per https://github.com/mpv-player/mpv/issues/10378.

This also failed to build without the `if OS.mac?` block that forces a selection of the SDK, though: https://github.com/Homebrew/homebrew-core/actions/runs/2735677980 Should we just insist on the Xcode SDK path everywhere?

> > That's what `depends_on :xcode => :build` insists, so it seems correct to do so here too unless you're planning to find a way to drop that? > >...

> the dylib issue needs sorting I agree it would be nicer to ship libraries as `dylib`s, but the linker seems to handle `MH_DYLIB`s with a `.so` extension just fine....