Re: PG vs macOS Mojave

From: Thomas Munro <thomas(dot)munro(at)enterprisedb(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: PG vs macOS Mojave
Date: 2018-09-25 22:58:44
Message-ID: CAEepm=16o51oMvY6K-E_mpSR6mPjm-zgDgY6_RE1VJGriLDPtA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, Sep 26, 2018 at 3:14 AM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Thomas Munro <thomas(dot)munro(at)enterprisedb(dot)com> writes:
> > On Tue, Sep 25, 2018 at 4:49 PM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2018-09-25 23:08:19 Re: [HACKERS] Support for Secure Transport SSL library on macOS as OpenSSL alternative
Previous Message Michael Paquier 2018-09-25 22:42:23 Re: Allowing printf("%m") only where it actually works