py310-pytomlpp @1.0.11: error: invalid value 'c++17' in '-std=c++17'

[ryandesign (Ryan Carsten Schmidt)]

​https://build.macports.org/builders/ports-10.10_x86_64-builder/builds/184918/steps/install-port/logs/stdio

/opt/local/var/macports/build/_opt_bblocal_var_buildworker_ports_build_ports_python_py-pytomlpp/py310-pytomlpp/work/compwrap/cc/usr/bin/clang -Wno-unused-result -Wsign-compare -Wunreachable-code -fno-common -dynamic -DNDEBUG -g -fwrapv -O3 -Wall -pipe -Os -arch x86_64 -isysroot/ -I/opt/local/var/macports/build/_opt_bblocal_var_buildworker_ports_build_ports_python_py-pytomlpp/py310-pytomlpp/work/pytomlpp-1.0.11/include -I/opt/local/var/macports/build/_opt_bblocal_var_buildworker_ports_build_ports_python_py-pytomlpp/py310-pytomlpp/work/pytomlpp-1.0.11/third_party -I/opt/local/Library/Frameworks/Python.framework/Versions/3.10/lib/python3.10/site-packages/pybind11/include -I/opt/local/Library/Frameworks/Python.framework/Versions/3.10/include/python3.10 -c src/encoding_decoding.cpp -o build/temp.macosx-10.10-x86_64-cpython-310/src/encoding_decoding.o -std=c++17
error: invalid value 'c++17' in '-std=c++17'

So on the one hand the portfile probably needs compiler.cxx_standard 2017 to make MacPorts select a C++17-capable compiler, but on the other hand it's weird to be sending -std=c++17 to a C compiler.

[ryandesign (Ryan Carsten Schmidt)]

Or rather, it's weird to be trying to compile a C++ file with a C compiler. But as we know Python doesn't support writing modules in C++ so this nonsense is apparently inevitable as long as developers continue to insist on writing Python modules in C++...

[Schamschula (Marius Schamschula)]

In ed3a9ef69bc40fa72e682f41264cf36f6fd61129/macports-ports (master):

py-pytomlpp: attem,pt to fix build

See: #65382

[Schamschula (Marius Schamschula)]

Oddly, this does fix it!