[MacPorts] #62944: grpc: py-grpcio port build failures, when compiler wrapping enabled (was: grpc: py-grpcio port build failures)
MacPorts
noreply at macports.org
Fri May 21 18:46:35 UTC 2021
#62944: grpc: py-grpcio port build failures, when compiler wrapping enabled
-----------------------------+------------------------------------
Reporter: mascguy | Owner: cjones051073
Type: defect | Status: assigned
Priority: Normal | Milestone:
Component: ports | Version:
Resolution: | Keywords: portgroup compilerwrap
Port: grpc py-grpcio |
-----------------------------+------------------------------------
Changes (by mascguy):
* keywords: => portgroup compilerwrap
Old 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
>
> Is it possible that we have a bug in one of our portgroups?
New description:
Some rather 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*'
[...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
UPDATE: Per discussion with @CJones in the comments, this occurs when
compiler wrapping is enabled. For now, the port has been updated to
disable said wrapping, to fix build failures. But keeping this ticket open
to track the wrapping issue.
--
--
Ticket URL: <https://trac.macports.org/ticket/62944#comment:22>
MacPorts <https://www.macports.org/>
Ports system for macOS
More information about the macports-tickets
mailing list