Horton

Re: PG vs macOS Mojave

Thomas Munro <thomas.munro@enterprisedb.com>

View thread View on postgr.es
From: Thomas Munro <thomas.munro@enterprisedb.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Date: 2018-09-25T22:58:44Z
Lists: pgsql-hackers 
On Wed, Sep 26, 2018 at 3:14 AM Tom Lane <tgl@sss.pgh.pa.us> wrote:
> Thomas Munro <thomas.munro@enterprisedb.com> writes:
> > On Tue, Sep 25, 2018 at 4:49 PM Tom Lane <tgl@sss.pgh.pa.us> wrote:
> >> I've tested this on all the macOS versions I have at hand, and it
> >> doesn't seem to break anything.  Only part (1) could possibly
> >> affect other platforms, and that seems safe enough.
> >>
> >> I'd like to commit and backpatch this, because otherwise longfin
> >> is going to start falling over when I upgrade its host to Mojave.
>
> > Looks good on this 10.13.4 system.  About to upgrade to 10.14...
>
> Thanks for testing!  I'll set to work on back-patching that.

... and now I'm on macOS 10.14.  I removed all traces of MacPorts from
my PATH and configure line to test this.  --with-tcl worked, but
--with-perl couldn't find "perl.h".  Then I realised that it was
because I was still on Xcode 9, so I was in for another ~5GB of
upgrading to get to Xcode 10.  After that, it all worked fine.


--
Thomas Munro
http://www.enterprisedb.com

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").