| 3 | | Is the point here to use Macports clang, as opposed to Xcode clang? Or ro use macports-clang-12, as opposed to, e.g., macports-clang-14? |
| | 3 | ~~Is the point here to use Macports clang, as opposed to Xcode clang? Or ro use macports-clang-12, as opposed to, e.g., macports-clang-14?~~ |
| | 4 | |
| | 5 | Answered my own question: it has to be Macports clang-12, newer compilers fail with the given error. |
| | 6 | |
| | 7 | Upstream has not reacted so far, and the last commit in the upstream repo was in 2020. |
| | 8 | |
| | 9 | I'm afraid it's up to us (this community) to provide a workaround/fix that allows building with clang-13 or newer. If I knew how to fix it, I'd propose it already. |
