[MacPorts] #63351: py-grpcio fails to build

[MacPorts]

#63351: py-grpcio fails to build
-------------------------+--------------------------
  Reporter:  mouse07410  |      Owner:  emcrisostomo
      Type:  defect      |     Status:  assigned
  Priority:  Normal      |  Milestone:
 Component:  ports       |    Version:
Resolution:              |   Keywords:
      Port:  py-grpcio   |
-------------------------+--------------------------

Comment (by mouse07410):

 > We haven't heard yet if you have the SDK that MacPorts appears to be
 actually trying to use
 > {{{/Library/Developer/CommandLineTools/SDKs/MacOSX11.sdk}}}

 No, of course not. CLT has a bug that prevents Haskell GHC from working
 correctly, so none of my machines has it.

 Why is Macports trying to use CLT, when the
 {{{work/compwrap/cc/usr/bin/clang}}} clearly (and almost correctly!)
 points at the {{{Xcode.app}}}? See
 {{{
 $ cat
 /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_devel_grpc/py39-grpcio/work/compwrap/cc/usr/bin/clang
 #!/bin/bash
 exec /usr/bin/clang   -Os -I/opt/local/include
 -isysroot/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX11.3.sdk
 -pipe ${MACPORTS_LEGACY_SUPPORT_CPPFLAGS}  "${@}"
 }}}

 In any case, (a) the build seems to proceed to 100% mark (as indicated by
 the port progress bar), and then fails, (b) there's about 900 ports on one
 machine and 1070 ports on another one - they all seem to build fine (yeah,
 some are pulled as binaries, but enough get rebuilt from sources to
 validate my setup in general).

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