[MacPorts] #62959: py-grpcio: various buildbot failures

[MacPorts]

#62959: py-grpcio: various buildbot failures
-----------------------------+----------------------
  Reporter:  mascguy         |      Owner:  mascguy
      Type:  defect          |     Status:  assigned
  Priority:  Normal          |  Milestone:
 Component:  ports           |    Version:
Resolution:                  |   Keywords:
      Port:  grpc py-grpcio  |
-----------------------------+----------------------
Description changed by mascguy:

Old description:

> There are a few different issues with this port build, depending on the
> platform.
>
> The following is what we're seeing for the latest buildbot jobs:
>
> Big Sur x86_64:
>
> https://build.macports.org/builders/ports-
> 11_x86_64-builder/builds/31390/steps/install-port/logs/stdio
>
> {{{
> distutils.errors.DistutilsPlatformError: $MACOSX_DEPLOYMENT_TARGET
> mismatch: now "11.0" but "11.2" during configure
> }}}
>
> 10.6:
>
> https://build.macports.org/builders/ports-10.6_x86_64-builder/builds/57438/steps
> /install-port/logs/stdio
>
> {{{
> error: invalid argument '-std=c++11' not allowed with 'C'
> }}}
>
> For 10.8/10.9:
>
> https://build.macports.org/builders/ports-10.8_x86_64-builder/builds/47452/steps
> /install-port/logs/stdio
>
> https://build.macports.org/builders/ports-10.9_x86_64-builder/builds/147853/steps
> /install-port/logs/stdio
>
> {{{
> In file included from src/core/lib/iomgr/gethostname_sysconf.cc:26:
> In file included from /opt/local/include/LegacySupport/unistd.h:92:
> In file included from /usr/include/unistd.h:72:
> /opt/local/include/LegacySupport/sys/unistd.h:76:16: error: unknown type
> name 'size_t'
>                          void *buf, size_t size, uint32_t flags);
>                                     ^
> }}}
>
> This might be a case of blacklisting older clang versions, and perhaps
> blacklisting Xcode clang entirely (if necessary).

New description:

 There are a few different issues with this port build, depending on the
 platform.

 The following is what we're seeing for the latest buildbot jobs:

 Big Sur x86_64:

 https://build.macports.org/builders/ports-
 11_x86_64-builder/builds/31390/steps/install-port/logs/stdio

 {{{
 distutils.errors.DistutilsPlatformError: $MACOSX_DEPLOYMENT_TARGET
 mismatch: now "11.0" but "11.2" during configure
 }}}

 10.6:

 https://build.macports.org/builders/ports-10.6_x86_64-builder/builds/57438/steps
 /install-port/logs/stdio

 {{{
 error: invalid argument '-std=c++11' not allowed with 'C'
 }}}

 For 10.7 through 10.9:

 https://build.macports.org/builders/ports-10.7_x86_64-builder/builds/53892/steps
 /install-port/logs/stdio

 https://build.macports.org/builders/ports-10.8_x86_64-builder/builds/47452/steps
 /install-port/logs/stdio

 https://build.macports.org/builders/ports-10.9_x86_64-builder/builds/147853/steps
 /install-port/logs/stdio

 {{{
 In file included from src/core/lib/iomgr/gethostname_sysconf.cc:26:
 In file included from /opt/local/include/LegacySupport/unistd.h:92:
 In file included from /usr/include/unistd.h:72:
 /opt/local/include/LegacySupport/sys/unistd.h:76:16: error: unknown type
 name 'size_t'
                          void *buf, size_t size, uint32_t flags);
                                     ^
 }}}

 This might be a case of blacklisting older clang versions, and perhaps
 blacklisting Xcode clang entirely (if necessary).

--

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