Horton

Re: PG vs macOS Mojave

Tom Lane <tgl@sss.pgh.pa.us>

View thread View on postgr.es
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
Cc: Daniel Gustafsson <daniel@yesql.se>, Jakob Egger <jakob@eggerapps.at>, pgsql-hackers@lists.postgresql.org
Date: 2018-11-02T14:42:21Z
Lists: pgsql-hackers 
I wrote:
> Here's a lightly-tested patch for that approach.

Anybody have an opinion about which approach to use?  We need to choose
one, and PDQ too, if we want full buildfarm coverage on it before Monday's
wrap.

The main argument in favor of #1 (restore use of -isysroot) is fear that
Apple's going to force us into that sometime soon anyhow, so we might as
well just bite the bullet instead of inserting weird workarounds to avoid
it.  But perhaps that isn't going to happen.  If it doesn't, then #2
(hack PLPerl and PLTcl include switches only) should result in slightly
less pain for people in Jakob's situation.  But either patch does offer
a workaround for that case.

			regards, tom lane

Commits

  1. Yet further rethinking of build changes for macOS Mojave.

  2. Still further rethinking of build changes for macOS Mojave.

  3. Back off using -isysroot on Darwin.

  4. Make some fixes to allow building Postgres on macOS 10.14 ("Mojave").