Yet further rethinking of build changes for macOS Mojave.

The solution arrived at in commit e74dd00f5 presumes that the compiler
has a suitable default -isysroot setting ... but further experience
shows that in many combinations of macOS version, XCode version, Xcode
command line tools version, and phase of the moon, Apple's compiler
will *not* supply a default -isysroot value.

We could potentially go back to the approach used in commit 68fc227dd,
but I don't have a lot of faith in the reliability or life expectancy of
that either.  Let's just revert to the approach already shipped in 11.0,
namely specifying an -isysroot switch globally.  As a partial response to
the concerns raised by Jakob Egger, adjust the contents of Makefile.global
to look like

CPPFLAGS = -isysroot $(PG_SYSROOT) ...
PG_SYSROOT = /path/to/sysroot

This allows overriding the sysroot path at build time in a relatively
painless way.

Add documentation to installation.sgml about how to use the PG_SYSROOT
option.  I also took the opportunity to document how to work around
macOS's "System Integrity Protection" feature.

As before, back-patch to all supported versions.

Discussion: https://postgr.es/m/20840.1537850987@sss.pgh.pa.us

diff --git a/configure b/configure
index 75007b05ab80c8f0254e153e7129af1f8f804014..bf2091a70fb7442fd11d06e50dece14c99ec9dc0 100755 (executable)
--- a/configure
+++ b/configure
@@ -627,6 +627,7 @@ ac_includes_default="\
 
 ac_subst_vars='LTLIBOBJS
 vpath_build
+PG_SYSROOT
 PG_VERSION_NUM
 PROVE
 OSX
@@ -16153,6 +16154,15 @@ _ACEOF
 
 
 
+# If we are inserting PG_SYSROOT into CPPFLAGS, do so symbolically not
+# literally, so that it's possible to override it at build time using
+# a command like "make ... PG_SYSROOT=path".  This has to be done after
+# we've finished all configure checks that depend on CPPFLAGS.
+if test x"$PG_SYSROOT" != x; then
+  CPPFLAGS=`echo "$CPPFLAGS" | sed -e "s| $PG_SYSROOT | \\\$(PG_SYSROOT) |"`
+fi
+
+
 
 # Begin output steps
 

diff --git a/configure.in b/configure.in
index 7004de09c9ff7768bbcb399f35e39695751c14a6..36927ccc5ec6526ae25e1afe6b7eb5562941fc63 100644 (file)
--- a/configure.in
+++ b/configure.in
@@ -2202,6 +2202,15 @@ $AWK '{printf "%d%02d%02d", $1, $2, (NF >= 3) ? $3 : 0}'`"]
 AC_DEFINE_UNQUOTED(PG_VERSION_NUM, $PG_VERSION_NUM, [PostgreSQL version as a number])
 AC_SUBST(PG_VERSION_NUM)
 
+# If we are inserting PG_SYSROOT into CPPFLAGS, do so symbolically not
+# literally, so that it's possible to override it at build time using
+# a command like "make ... PG_SYSROOT=path".  This has to be done after
+# we've finished all configure checks that depend on CPPFLAGS.
+if test x"$PG_SYSROOT" != x; then
+  CPPFLAGS=`echo "$CPPFLAGS" | sed -e "s| $PG_SYSROOT | \\\$(PG_SYSROOT) |"`
+fi
+AC_SUBST(PG_SYSROOT)
+
 
 # Begin output steps
 

diff --git a/doc/src/sgml/installation.sgml b/doc/src/sgml/installation.sgml
index d3088a3101ff55ef90dc38dd18831afcf6e59ac2..bd75eae90511e3a30c9d8b84e85d10c782cc90b7 100644 (file)
--- a/doc/src/sgml/installation.sgml
+++ b/doc/src/sgml/installation.sgml
@@ -2596,6 +2596,57 @@ PHSS_30849  s700_800 u2comp/be/plugin library Patch
    
   
 
+  
+   macOS
+
+   
+    macOS
+    installation on
+   
+
+   
+    On recent macOS releases, it's necessary to
+    embed the sysroot path in the include switches used to
+    find some system header files.  This results in the outputs of
+    the configure script varying depending on
+    which SDK version was used during configure.
+    That shouldn't pose any problem in simple scenarios, but if you are
+    trying to do something like building an extension on a different machine
+    than the server code was built on, you may need to force use of a
+    different sysroot path.  To do that, set PG_SYSROOT,
+    for example
+
+make PG_SYSROOT=/desired/path all
+
+    To find out the appropriate path on your machine, run
+
+xcodebuild -version -sdk macosx Path
+
+    Note that building an extension using a different sysroot version than
+    was used to build the core server is not really recommended; in the
+    worst case it could result in hard-to-debug ABI inconsistencies.
+   
+
+   
+    You can also select a non-default sysroot path when configuring, by
+    specifying PG_SYSROOT
+    to configure:
+
+./configure ... PG_SYSROOT=/desired/path
+
+   
+
+   
+    macOS's System Integrity
+    Protection (SIP) feature breaks make check,
+    because it prevents passing the needed setting
+    of DYLD_LIBRARY_PATH down to the executables being
+    tested.  You can work around that by doing make
+    install before make check.
+    Most Postgres developers just turn off SIP, though.
+   
+  
+
   
    MinGW/Native Windows
 

diff --git a/src/Makefile.global.in b/src/Makefile.global.in
index d52ae8c0578f0e97afd6219d74e6731dd0247acc..d21ef854a49c3c09e64b44363044af641e49a46d 100644 (file)
--- a/src/Makefile.global.in
+++ b/src/Makefile.global.in
@@ -226,6 +226,7 @@ PTHREAD_LIBS        = @PTHREAD_LIBS@
 
 CPP = @CPP@
 CPPFLAGS = @CPPFLAGS@
+PG_SYSROOT = @PG_SYSROOT@
 
 ifdef PGXS
 override CPPFLAGS := -I$(includedir_server) -I$(includedir_internal) $(CPPFLAGS)

diff --git a/src/template/darwin b/src/template/darwin
index 159d8bb12750f698bd48e6f0ae0a53f958aca3b9..c05adca0bfbec7bba7a6551d4edf0ea0bf932d49 100644 (file)
--- a/src/template/darwin
+++ b/src/template/darwin
@@ -3,14 +3,15 @@
 # Note: Darwin is the original code name for macOS, also known as OS X.
 # We still use "darwin" as the port name, partly because config.guess does.
 
-# Some configure tests require explicit knowledge of where the Xcode "sysroot"
-# is.  We try to avoid having this leak into configure's results, though.
+# Select where system include files should be sought.
 if test x"$PG_SYSROOT" = x"" ; then
   PG_SYSROOT=`xcodebuild -version -sdk macosx Path 2>/dev/null`
 fi
 # Old xcodebuild versions may produce garbage, so validate the result.
 if test x"$PG_SYSROOT" != x"" ; then
-  if test \! -d "$PG_SYSROOT" ; then
+  if test -d "$PG_SYSROOT" ; then
+    CPPFLAGS="-isysroot $PG_SYSROOT $CPPFLAGS"
+  else
     PG_SYSROOT=""
   fi
 fi