[MacPorts] #70563: py310-grpcio @1.48.4_9: error: no member named 'in_place_t' in namespace 'std'

[MacPorts]

#70563: py310-grpcio @1.48.4_9: error: no member named 'in_place_t' in namespace
'std'
----------------------+--------------------------
  Reporter:  areilly  |      Owner:  emcrisostomo
      Type:  defect   |     Status:  assigned
  Priority:  Normal   |  Milestone:
 Component:  ports    |    Version:
Resolution:           |   Keywords:
      Port:  grpc     |
----------------------+--------------------------
Changes (by ryandesign):

 * cc: essandess (added)


Comment:

 Replying to [comment:5 jmroot]:
 > grpc: try to actually use C++17

 Looks like that fixed one place in the build system where it specified
 C++14 but there are still others.

 Here is the [https://github.com/grpc/grpc/issues/34256 grpc bug report]
 from over a year ago about the forced use of C++14 causing compatibility
 issues when trying to use a system abseil or re2 that needs C++17. No
 solution is posted there.

 grpc upstream has
 [https://github.com/grpc/grpc/commit/93b29607ccaa2545e2b3a5a8016f765333f1b38f
 only just last week switched to C++17] and no release contains that change
 yet.

 Replying to [comment:4 jmroot]:
 > Updating is likely still the best fix.

 The port is very complicated and the person who prepares the update will
 need to be an expert who understands everything the port is doing, and
 also understands the grpc build system and the ways in which it has
 evolved over the years. Steve, you're the one who
 [changeset:c4ba306bbea288e59108a0e785d3b7d08eaf5ba8/macports-ports
 converted the port to its current complicated form] so you probably
 understand it best. Would you like to do the update and/or a patch to make
 it use C++17?

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