[MacPorts] #62944: grpc: py-grpcio port build failures (was: grpc: py-grpcio port build failures for arm)

[MacPorts]

#62944: grpc: py-grpcio port build failures
-----------------------------+--------------------
  Reporter:  mascguy         |      Owner:  (none)
      Type:  defect          |     Status:  new
  Priority:  Normal          |  Milestone:
 Component:  ports           |    Version:
Resolution:                  |   Keywords:
      Port:  grpc py-grpcio  |
-----------------------------+--------------------
Changes (by mascguy):

 * keywords:  arm =>


Old description:

> Some rather, well, interesting build errors, are occurring on our ARM
> buildbot:
>
> {{{
> [...]
> clang: error: no such file or directory: '"C"'
> clang: error: no such file or directory: '__attribute__((visibility'
> clang: error: no such file or directory: '("default")))'
> clang: error: no such file or directory: 'PyObject*'
> clang: error: clangno such file or directory: '("default")))': error: no
> such file or directory: '("default")))'
> [...etc...]
> }}}
>
> That's from this example, for `py39-grpcio`:
> https://build.macports.org/builders/ports-
> 11_arm64-builder/builds/20741/steps/install-port/logs/stdio
>
> Full log also attached; filename: py39-grpcio-buildbot-failure-arm.txt.gz
>
> Is it possible that we have a bug in one of our portgroups?

New description:

 Some rather, well, interesting build errors, are occurring across all of
 our buildbots:

 {{{
 [...]
 clang: error: no such file or directory: '"C"'
 clang: error: no such file or directory: '__attribute__((visibility'
 clang: error: no such file or directory: '("default")))'
 clang: error: no such file or directory: 'PyObject*'
 clang: error: clangno such file or directory: '("default")))': error: no
 such file or directory: '("default")))'
 [...etc...]
 }}}

 That's from this example, for `py39-grpcio`:
 https://build.macports.org/builders/ports-
 11_arm64-builder/builds/20741/steps/install-port/logs/stdio

 Full log also attached; filename: py39-grpcio-buildbot-failure-arm.txt.gz

 Note that this is occurring across all of our buildbots though, so it's
 not ARM-specific.

 Is it possible that we have a bug in one of our portgroups?

--

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