[MacPorts] #59078: poppler @0.80.0 build fails with Xcode 11.0

[MacPorts]

#59078: poppler @0.80.0 build fails with Xcode 11.0
--------------------------------------------+----------------------
  Reporter:  mndavidoff                     |      Owner:  dbevans
      Type:  defect                         |     Status:  assigned
  Priority:  Normal                         |  Milestone:
 Component:  ports                          |    Version:
Resolution:                                 |   Keywords:  xcode11
      Port:  poppler gobject-introspection  |
--------------------------------------------+----------------------

Comment (by dbevans):

 Replying to [comment:24 MarcusCalhoun-Lopez]:
 > I wold argue that there are **two** issues that need to be fixed:
 > 1. Prevent Python (and Pearl)  from passing build time configurations to
 other ports (as you said).
 > 1. Have ports respect `${configure.sdkroot}`.
 > I may be missing something, but it seems that this is a general
 solution.\\
 > If we prevent Python from passing `-isysroot` to its ports, then
 **something** has to force `g-ir-scanner` to use the correct `-isysroot`.

 Unfortunately, perl and python have a good reason for the way they pass
 the build time configuration. The primary use case that they are
 interested in is the building of perl, python extensions.  Passing the
 build time parameters ensures that the extensions are built in the same
 environment as the current libpython, libperl, ensuring compatibility.
 gobject-introspection is an odd case because it doesn't link with those
 libraries, but would benefit from rebuilding libpython with Xcode 11 as
 would the many ports that produce python extensions. I'm not entirely
 familiar with the internals of how python does this but with perl the
 mechanism is deeply ingrained into the build philosophy and tools
 generally.

 The real problem here is that Xcode 11 requires a different sysroot than
 the previous Xcode 10 and is therefore not fully compatible.  My political
 statement for the day is that it is a shame that they didn't retain the
 old 10.14 sysroot for Xcode 11 on 10.14.  Things would have been much
 easier and, of course, the ultimate solution is to not use Xcode 11 on
 10.14 unless there is a compelling need.  This is really a Mojave corner
 case that can be avoided.  Catalina should be released before long and
 start a clean slate for Xcode 11.

 At any rate, I think we can both agree that we (or at least I) need to
 understand the python build mechanism better and refine our solution
 before merging the gobject-introspection PR.  So I proposed to keep the PR
 open but mark it WIP, not to be merged until we have a better handle on
 this issue.

-- 
Ticket URL: <https://trac.macports.org/ticket/59078#comment:25>
MacPorts <https://www.macports.org/>
Ports system for macOS