[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 MarcusCalhoun-Lopez):

 Replying to [comment:21 dbevans]:
 > Replying to [comment:20 MarcusCalhoun-Lopez]:
 > > Replying to [comment:18 dbevans]:
 > > > Replying to [comment:17 MarcusCalhoun-Lopez]:
 > > > > There is a [https://github.com/macports/macports-ports/pull/5385
 pull request] that attempts to resolve this issue (at least for the ports
 that use gobject-introspection).
 > > >
 > > > Since this issue is not limited to gobject-introspection and can be
 fixed by rebuilding with Xcode11 (specific ports if not all) I hesitate to
 apply this pull request that only addresses the symptoms of gobject-
 introspection and not the root cause.
 > >
 > > May I humbly suggest that the [https://github.com/macports/macports-
 ports/pull/5385 pull request] is neither a hack nor even a workaround.\\
 > > As much as possible, ports should respect MacPorts settings, which
 includes `${configure.sdkroot}`.\\
 > > Even if we successfully rebuild all of the ports with Xcode 11, I
 would argue that we should still apply the patch.\\
 > > The Xcode 11 problem simply revealed an issue with the
 gobject_introspection PortGroup.
 >
 > I disagree since the root cause seems to be that python passes its build
 time configuration to ports that build binaries (as does perl).  So I hold
 that rebuilding python against Xcode11 should fix the issue as well as
 potential issues with other python ports that build binaries. I would
 prefer a more global solution.

 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`.

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