James Hilliard <james.hillia...@gmail.com> writes: > On Tue, Jan 19, 2021 at 8:27 AM Tom Lane <t...@sss.pgh.pa.us> wrote: >> We already dealt with that by not selecting an SDK newer than the >> underlying OS (see 4823621db).
> Tried that, doesn't work, not even sure how it could possibly fix this > issue at all, It worked for me and for Sergey, so we need to figure out what's different about your setup. What do you get from "xcrun --show-sdk-path" and "xcrun --sdk macosx --show-sdk-path"? What have you got under /Library/Developer/CommandLineTools/SDKs ? > this can not be fixed properly by selecting a specific SDK version > alone, it's the symbols valid for a specific target deployment version > that matters here. I don't think I believe that argument. As a counterexample, supposing that somebody were intentionally cross-compiling on an older OSX platform but using a newer SDK, shouldn't they get an executable suited to the SDK's target version? (I realize that Apple thinks we ought to handle that through run-time not compile-time adaptation, but I have no interest in going there.) regards, tom lane